USN-6652-1: Linux kernel (Azure) vulnerabilities

Published Feb 23, 2024
·
Updated

Marek Marczykowski-Górecki discovered that the Xen event channel infrastructure implementation in the Linux kernel contained a race condition. An attacker in a guest VM could possibly use this to cause a denial of service (paravirtualized device unavailability). (CVE-2023-34324) Zheng Wang discovered a use-after-free in the Renesas Ethernet AVB driver in the Linux kernel during device removal. A privileged attacker could use this to cause a denial of service (system crash). (CVE-2023-35827) Tom Dohrmann discovered that the Secure Encrypted Virtualization (SEV) implementation for AMD processors in the Linux kernel contained a race condition when accessing MMIO registers. A local attacker in a SEV guest VM could possibly use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-46813) It was discovered that the iouring subsystem in the Linux kernel contained a race condition, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-46862) It was discovered that a race condition existed in the ATM (Asynchronous Transfer Mode) subsystem of 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-2023-51780) It was discovered that a race condition existed in the AppleTalk networking subsystem of 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-2023-51781) It was discovered that the netfilter subsystem in the Linux kernel did not properly validate inner tunnel netlink attributes, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-5972) It was discovered that the TLS subsystem in the Linux kernel did not properly perform cryptographic operations in some situations, leading to 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-6176) Jann Horn discovered that a race condition existed in the Linux kernel when handling iouring over sockets, 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-6531) Xingyuan Mo discovered that the netfilter subsystem in the Linux kernel did not properly handle dynset expressions passed from userspace, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-6622) Zhenghan Wang discovered that the generic ID allocator implementation in the Linux kernel did not properly check for null bitmap when releasing IDs. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-6915) Robert Morris discovered that the CIFS network file system implementation in the Linux kernel did not properly validate certain server commands fields, leading to an out-of-bounds read vulnerability. An attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2024-0565) Jann Horn discovered that the iouring subsystem in the Linux kernel did not properly handle the release of certain buffer rings. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-0582) It was discovered that the TIPC protocol implementation in the Linux kernel did not properly handle locking during tipccryptokeyrevoke() operations. A local attacker could use this to cause a denial of service (kernel deadlock). (CVE-2024-0641) Jann Horn discovered that the TLS subsystem in the Linux kernel did not properly handle spliced messages, leading to 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-2024-0646)

Affected Software

9 affected componentsFixes available
Microsoft Linux kernel (Azure)
All of the following
ubuntu/linux-image-6.5.0-1015-azure<6.5.0-1015.15
6.5.0-1015.15
Ubuntu Ubuntu=23.10
All of the following
ubuntu/linux-image-6.5.0-1015-azure-fde<6.5.0-1015.15
6.5.0-1015.15
Ubuntu Ubuntu=23.10
All of the following
ubuntu/linux-image-azure<6.5.0.1015.17
6.5.0.1015.17
Ubuntu Ubuntu=23.10
All of the following
ubuntu/linux-image-azure-fde<6.5.0.1015.17
6.5.0.1015.17
Ubuntu Ubuntu=23.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-6.5.0-1015-azure to a version that resolves this vulnerability.

    Fixed in 6.5.0-1015.15
  2. Upgrade

    Upgrade ubuntu/linux-image-6.5.0-1015-azure-fde to a version that resolves this vulnerability.

    Fixed in 6.5.0-1015.15
  3. Upgrade

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

    Fixed in 6.5.0.1015.17
  4. Upgrade

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

    Fixed in 6.5.0.1015.17

Event History

Feb 23, 2024
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of USN-6652-1?

The severity of USN-6652-1 is classified as a denial of service vulnerability.

2

How do I fix USN-6652-1?

To fix USN-6652-1, you should update to the latest package versions as specified in the advisory.

3

What products are affected by USN-6652-1?

The affected products by USN-6652-1 include specific versions of the Ubuntu Linux kernel packages.

4

Can USN-6652-1 be exploited remotely?

Yes, USN-6652-1 can be exploited by an attacker in a guest VM environment.

5

Is it safe to remain on an outdated version after USN-6652-1?

No, it is not safe to remain on an outdated version, as it poses a risk of potential denial of service attacks.

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