USN-6626-2: Linux kernel vulnerabilities

Published Feb 14, 2024
·
Updated

Quentin Minster discovered that a race condition existed in the KSMBD implementation in the Linux kernel when handling sessions operations. A remote attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-32250, CVE-2023-32252, CVE-2023-32257) 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 Microchip USB Ethernet driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2023-6039) 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) 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) 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)

Affected Software

14 affected componentsFixes available
All of the following
ubuntu/linux-image-5.15.0-1046-raspi<5.15.0-1046.49
5.15.0-1046.49
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-94-lowlatency<5.15.0-94.104
5.15.0-94.104
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-94-lowlatency-64k<5.15.0-94.104
5.15.0-94.104
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency<5.15.0.94.94
5.15.0.94.94
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency-64k<5.15.0.94.94
5.15.0.94.94
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-raspi<5.15.0.1046.44
5.15.0.1046.44
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-raspi-nolpae<5.15.0.1046.44
5.15.0.1046.44
Ubuntu Ubuntu=22.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.15.0-1046.49
  2. Upgrade

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

    Fixed in 5.15.0-94.104
  3. Upgrade

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

    Fixed in 5.15.0-94.104
  4. Upgrade

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

    Fixed in 5.15.0.94.94
  5. Upgrade

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

    Fixed in 5.15.0.94.94
  6. Upgrade

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

    Fixed in 5.15.0.1046.44
  7. Upgrade

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

    Fixed in 5.15.0.1046.44

Event History

Feb 14, 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-6626-2?

USN-6626-2 is considered to have a high severity due to its potential to cause denial of service and arbitrary code execution.

2

How do I fix USN-6626-2?

To fix USN-6626-2, update your Linux kernel to the recommended version listed in the advisory.

3

Which systems are affected by USN-6626-2?

USN-6626-2 affects Ubuntu 22.04 systems running specified versions of the Linux kernel.

4

Can USN-6626-2 be exploited remotely?

Yes, USN-6626-2 can be exploited remotely by an attacker to cause a denial of service or potentially execute arbitrary code.

5

What is the nature of the vulnerability in USN-6626-2?

The vulnerability in USN-6626-2 is a race condition in the KSMBD implementation of the Linux kernel.

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