USN-6175-1: Linux kernel vulnerabilities

Published Jun 16, 2023
·
Updated

Patryk Sondej and Piotr Krysiuk discovered that a race condition existed in the netfilter subsystem of the Linux kernel when processing batch requests, 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-32233) Gwangun Jung discovered that the Quick Fair Queueing scheduler implementation 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) or possibly execute arbitrary code. (CVE-2023-31436) Reima Ishii discovered that the nested KVM implementation for Intel x86 processors in the Linux kernel did not properly validate control registers in certain situations. An attacker in a guest VM could use this to cause a denial of service (guest crash). (CVE-2023-30456) It was discovered that the Broadcom FullMAC USB WiFi driver in the Linux kernel did not properly perform data buffer size validation 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 expose sensitive information. (CVE-2023-1380) William Zhao discovered that the Traffic Control (TC) subsystem in the Linux kernel did not properly handle network packet retransmission in certain situations. A local attacker could use this to cause a denial of service (kernel deadlock). (CVE-2022-4269) It was discovered that the iouring subsystem in the Linux kernel did not properly perform file table updates in some situations, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-1583) It was discovered that a race condition existed in the btrfs file system implementation 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 expose sensitive information. (CVE-2023-1611) It was discovered that the Xircom PCMCIA network device driver in the Linux kernel did not properly handle device removal events. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2023-1670) It was discovered that the APM X-Gene SoC hardware monitoring driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or expose sensitive information (kernel memory). (CVE-2023-1855) It was discovered that a race condition existed in the Xen transport layer implementation for the 9P file system protocol in the Linux kernel, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (guest crash) or expose sensitive information (guest kernel memory). (CVE-2023-1859) It was discovered that a race condition existed in the Bluetooth HCI SDIO driver, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-1989) It was discovered that the ST NCI NFC driver did not properly handle device removal events. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2023-1990) It was discovered that the SLIMpro I2C device driver in the Linux kernel did not properly validate user-supplied data in some situations, leading to an out-of-bounds write vulnerability. A privileged attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-2194) It was discovered that the perf subsystem in the Linux kernel contained a use-after-free vulnerability. A privileged local attacker could possibly use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-2235) Jean-Baptiste Cayrou discovered that the shiftfs file system in the Ubuntu Linux kernel contained a race condition when handling inode locking in some situations. A local attacker could use this to cause a denial of service (kernel deadlock). (CVE-2023-2612) It was discovered that a race condition existed in the TLS subsystem in the Linux kernel, leading to a use-after-free or a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-28466) It was discovered that the Bluetooth subsystem in the Linux kernel did not properly initialize some data structures, leading to an out-of-bounds access vulnerability in certain situations. An attacker could use this to expose sensitive information (kernel memory). (CVE-2023-28866) It was discovered that the DA9150 charger driver in the Linux kernel did not properly handle device removal, leading to a user-after free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-30772) It was discovered that the Qualcomm EMAC ethernet driver in the Linux kernel did not properly handle device removal, leading to a user-after free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-33203) It was discovered that the BQ24190 charger driver in the Linux kernel did not properly handle device removal, leading to a user-after free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-33288)

Affected Software

35 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-virtual<6.2.0.23.23
6.2.0.23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-generic-64k<6.2.0.23.23
6.2.0.23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-generic<6.2.0.23.23
6.2.0.23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-aws<6.2.0.1005.6
6.2.0.1005.6
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-raspi<6.2.0.1006.9
6.2.0.1006.9
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-lowlatency-64k<6.2.0.1005.5
6.2.0.1005.5
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-23-generic-64k<6.2.0-23.23
6.2.0-23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-1005-aws<6.2.0-1005.5
6.2.0-1005.5
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-raspi-nolpae<6.2.0.1006.9
6.2.0.1006.9
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-1006-raspi<6.2.0-1006.8
6.2.0-1006.8
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-23-generic<6.2.0-23.23
6.2.0-23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-1005-lowlatency<6.2.0-1005.5
6.2.0-1005.5
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-1005-lowlatency-64k<6.2.0-1005.5
6.2.0-1005.5
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-23-generic-lpae<6.2.0-23.23
6.2.0-23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-generic-lpae<6.2.0.23.23
6.2.0.23.23
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-6.2.0-1006-raspi-nolpae<6.2.0-1006.8
6.2.0-1006.8
Ubuntu Ubuntu=23.04
All of the following
ubuntu/linux-image-lowlatency<6.2.0.1005.5
6.2.0.1005.5
Ubuntu Ubuntu=23.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-virtual to a version that resolves this vulnerability.

    Fixed in 6.2.0.23.23
  2. Upgrade

    Upgrade ubuntu/linux-image-generic-64k to a version that resolves this vulnerability.

    Fixed in 6.2.0.23.23
  3. Upgrade

    Upgrade ubuntu/linux-image-generic to a version that resolves this vulnerability.

    Fixed in 6.2.0.23.23
  4. Upgrade

    Upgrade ubuntu/linux-image-aws to a version that resolves this vulnerability.

    Fixed in 6.2.0.1005.6
  5. Upgrade

    Upgrade ubuntu/linux-image-raspi to a version that resolves this vulnerability.

    Fixed in 6.2.0.1006.9
  6. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 6.2.0.1005.5
  7. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-23-generic-64k to a version that resolves this vulnerability.

    Fixed in 6.2.0-23.23
  8. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-1005-aws to a version that resolves this vulnerability.

    Fixed in 6.2.0-1005.5
  9. Upgrade

    Upgrade ubuntu/linux-image-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 6.2.0.1006.9
  10. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-1006-raspi to a version that resolves this vulnerability.

    Fixed in 6.2.0-1006.8
  11. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-23-generic to a version that resolves this vulnerability.

    Fixed in 6.2.0-23.23
  12. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-1005-lowlatency to a version that resolves this vulnerability.

    Fixed in 6.2.0-1005.5
  13. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-1005-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 6.2.0-1005.5
  14. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-23-generic-lpae to a version that resolves this vulnerability.

    Fixed in 6.2.0-23.23
  15. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae to a version that resolves this vulnerability.

    Fixed in 6.2.0.23.23
  16. Upgrade

    Upgrade ubuntu/linux-image-6.2.0-1006-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 6.2.0-1006.8
  17. Upgrade

    Upgrade ubuntu/linux-image-lowlatency to a version that resolves this vulnerability.

    Fixed in 6.2.0.1005.5
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch USN-6175-1

Event History

Jun 16, 2023
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this Linux kernel vulnerability?

The vulnerability ID for this Linux kernel vulnerability is USN-6175-1.

2

What is the severity of USN-6175-1?

The severity of USN-6175-1 is not mentioned in the description.

3

How does this vulnerability occur?

This vulnerability occurs due to a race condition in the netfilter subsystem of the Linux kernel when processing batch requests.

4

What is the impact of this vulnerability?

The impact of this vulnerability is a use-after-free vulnerability that could allow a local attacker to cause a denial of service (system crash) or possibly execute arbitrary code.

5

How do I fix USN-6175-1?

To fix USN-6175-1, update your Linux kernel to version 6.2.0.23.23 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203