Skip to content
OpenAdvisories
High 1 exploited CVE USN-5975-1 31 CVEs

linux-azure vulnerabilities

Published Mar 27, 2023 · Updated Oct 23, 2026

Ecosystem: Ubuntu

Summary

Updated on 2023-04-11:
Please note that when USN 5975-1 was originally published, it incorrectly
included the linux-gcp kernel for Ubuntu 16.04 ESM. References to that
kernel have been removed from this USN and the correct information for it
has been published in USN 6007-1.

Original advisory details:

It was discovered that the Upper Level Protocol (ULP) subsystem in the
Linux kernel did not properly handle sockets entering the LISTEN state in
certain protocols, leading to a use-after-free vulnerability. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2023-0461)

It was discovered that the System V IPC implementation in the Linux kernel
did not properly handle large shared memory counts. A local attacker could
use this to cause a denial of service (memory exhaustion). (CVE-2021-3669)

It was discovered that an out-of-bounds write vulnerability existed in the
Video for Linux 2 (V4L2) implementation in the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2022-20369)

Pawan Kumar Gupta, Alyssa Milburn, Amit Peled, Shani Rehana, Nir Shildan
and Ariel Sabba discovered that some Intel processors with Enhanced
Indirect Branch Restricted Speculation (eIBRS) did not properly handle RET
instructions after a VM exits. A local attacker could potentially use this
to expose sensitive information. (CVE-2022-26373)

David Leadbeater discovered that the netfilter IRC protocol tracking
implementation in the Linux Kernel incorrectly handled certain message
payloads in some situations. A remote attacker could possibly use this to
cause a denial of service or bypass firewall filtering. (CVE-2022-2663)

Johannes Wikner and Kaveh Razavi discovered that for some AMD x86-64
processors, the branch predictor could by mis-trained for return
instructions in certain circumstances. A local attacker could possibly use
this to expose sensitive information. (CVE-2022-29900)

Johannes Wikner and Kaveh Razavi discovered that for some Intel x86-64
processors, the Linux kernel's protections against speculative branch
target injection attacks were insufficient in some circumstances. A local
attacker could possibly use this to expose sensitive information.
(CVE-2022-29901)

It was discovered that a use-after-free vulnerability existed in the SGI
GRU driver in the Linux kernel. A local attacker could possibly use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2022-3424)

It was discovered that a race condition existed in the Kernel Connection
Multiplexor (KCM) socket implementation in the Linux kernel when releasing
sockets in certain situations. A local attacker could use this to cause a
denial of service (system crash). (CVE-2022-3521)

It was discovered that the Netronome Ethernet driver in the Linux kernel
contained a use-after-free vulnerability. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2022-3545)

It was discovered that the Broadcom FullMAC USB WiFi driver in the Linux
kernel did not properly perform bounds checking in some situations. A
physically proximate attacker could use this to craft a malicious USB
device that when inserted, could cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2022-3628)

Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an out-of-bounds write vulnerability. A local attacker
could use this to cause a denial of service (system crash).
(CVE-2022-36280)

It was discovered that a use-after-free vulnerability existed in the
Bluetooth stack in the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2022-3640)

It was discovered that the NILFS2 file system implementation in the Linux
kernel did not properly deallocate memory in certain error conditions. An
attacker could use this to cause a denial of service (memory exhaustion).
(CVE-2022-3646)

Khalid Masum discovered that the NILFS2 file system implementation in the
Linux kernel did not properly handle certain error conditions, leading to a
use-after-free vulnerability. A local attacker could use this to cause a
denial of service or possibly execute arbitrary code. (CVE-2022-3649)

Hyunwoo Kim discovered that an integer overflow vulnerability existed in
the PXA3xx graphics driver in the Linux kernel. A local attacker could
possibly use this to cause a denial of service (system crash).
(CVE-2022-39842)

Hyunwoo Kim discovered that the DVB Core driver in the Linux kernel did not
properly perform reference counting in some situations, leading to a use-
after-free vulnerability. A local attacker could use this to cause a denial
of service (system crash) or possibly execute arbitrary code.
(CVE-2022-41218)

It was discovered that a race condition existed in the SMSC UFX USB driver
implementation in the Linux kernel, leading to a use-after-free
vulnerability. A physically proximate attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2022-41849)

It was discovered that a race condition existed in the Roccat HID driver in
the Linux kernel, leading to a use-after-free vulnerability. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2022-41850)

It was discovered that a race condition existed in the Xen network backend
driver in the Linux kernel when handling dropped packets in certain
circumstances. An attacker could use this to cause a denial of service
(kernel deadlock). (CVE-2022-42328, CVE-2022-42329)

Tamás Koczka discovered that the Bluetooth L2CAP implementation in the
Linux kernel did not properly initialize memory in some situations. A
physically proximate attacker could possibly use this to expose sensitive
i

Fixed packages 1

ReleasePackageFixed in
Ubuntu · Pro 16.04 LTS Pro:16.04:LTS linux-azure 4.15.0-1162.177~16.04.1

Vulnerabilities 31

References

  • report
    https://ubuntu.com/security/CVE-2021-3669
  • report
    https://ubuntu.com/security/CVE-2022-2663
  • report
    https://ubuntu.com/security/CVE-2022-3424
  • report
    https://ubuntu.com/security/CVE-2022-3521
  • report
    https://ubuntu.com/security/CVE-2022-3545
  • report
    https://ubuntu.com/security/CVE-2022-3628
  • report
    https://ubuntu.com/security/CVE-2022-3640
  • report
    https://ubuntu.com/security/CVE-2022-3646
  • report
    https://ubuntu.com/security/CVE-2022-3649
  • report
    https://ubuntu.com/security/CVE-2022-20369
  • report
    https://ubuntu.com/security/CVE-2022-26373
  • report
    https://ubuntu.com/security/CVE-2022-29900
  • report
    https://ubuntu.com/security/CVE-2022-29901
  • report
    https://ubuntu.com/security/CVE-2022-36280
  • report
    https://ubuntu.com/security/CVE-2022-39842
  • report
    https://ubuntu.com/security/CVE-2022-41218
  • report
    https://ubuntu.com/security/CVE-2022-41849
  • report
    https://ubuntu.com/security/CVE-2022-41850
  • report
    https://ubuntu.com/security/CVE-2022-42328
  • report
    https://ubuntu.com/security/CVE-2022-42329
  • report
    https://ubuntu.com/security/CVE-2022-42895
  • report
    https://ubuntu.com/security/CVE-2022-43750
  • report
    https://ubuntu.com/security/CVE-2022-47929
  • report
    https://ubuntu.com/security/CVE-2023-0045
  • report
    https://ubuntu.com/security/CVE-2023-0266
  • report
    https://ubuntu.com/security/CVE-2023-0394
  • report
    https://ubuntu.com/security/CVE-2023-0461
  • report
    https://ubuntu.com/security/CVE-2023-23455
  • report
    https://ubuntu.com/security/CVE-2023-23559
  • report
    https://ubuntu.com/security/CVE-2023-26607
  • report
    https://ubuntu.com/security/CVE-2023-28328