USN-6626-2: Linux kernel vulnerabilities
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-5.15.0-1046-raspito a version that resolves this vulnerability.Fixed in 5.15.0-1046.49 - Upgrade
Upgrade
ubuntu/linux-image-5.15.0-94-lowlatencyto a version that resolves this vulnerability.Fixed in 5.15.0-94.104 - Upgrade
Upgrade
ubuntu/linux-image-5.15.0-94-lowlatency-64kto a version that resolves this vulnerability.Fixed in 5.15.0-94.104 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 5.15.0.94.94 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-64kto a version that resolves this vulnerability.Fixed in 5.15.0.94.94 - Upgrade
Upgrade
ubuntu/linux-image-raspito a version that resolves this vulnerability.Fixed in 5.15.0.1046.44 - Upgrade
Upgrade
ubuntu/linux-image-raspi-nolpaeto a version that resolves this vulnerability.Fixed in 5.15.0.1046.44
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
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.
How do I fix USN-6626-2?
To fix USN-6626-2, update your Linux kernel to the recommended version listed in the advisory.
Which systems are affected by USN-6626-2?
USN-6626-2 affects Ubuntu 22.04 systems running specified versions of the Linux kernel.
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.
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.