USN-6412-1: Linux kernel vulnerabilities
Hyunwoo Kim discovered that the DVB Core 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) or possibly execute arbitrary code. (CVE-2022-45886, CVE-2022-45919) Hyunwoo Kim discovered that the Technotrend/Hauppauge USB DEC 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-2022-45887) It was discovered that the NTFS file system implementation in the Linux kernel did not properly validate MFT flags in certain situations. An attacker could use this to construct a malicious NTFS image that, when mounted and operated on, could cause a denial of service (system crash). (CVE-2022-48425) It was discovered that the IPv6 implementation in the Linux kernel contained a high rate of hash collisions in connection lookup table. A remote attacker could use this to cause a denial of service (excessive CPU consumption). (CVE-2023-1206) Daniel Trujillo, Johannes Wikner, and Kaveh Razavi discovered that some AMD processors utilising speculative execution and branch prediction may allow unauthorised memory reads via a speculative side-channel attack. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2023-20569) It was discovered that the IPv6 RPL protocol implementation in the Linux kernel did not properly handle user-supplied data. A remote attacker could use this to cause a denial of service (system crash). (CVE-2023-2156) Yang Lan discovered that the GFS2 file system implementation in the Linux kernel could attempt to dereference a null pointer in some situations. An attacker could use this to construct a malicious GFS2 image that, when mounted and operated on, could cause a denial of service (system crash). (CVE-2023-3212) It was discovered that the KSMBD implementation in the Linux kernel did not properly validate buffer sizes in certain operations, leading to an integer underflow and out-of-bounds read vulnerability. A remote attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2023-38427) Chih-Yen Chang discovered that the KSMBD implementation in the Linux kernel did not properly validate packet header sizes in certain situations, leading to an out-of-bounds read vulnerability. A remote attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2023-38431) Andy Nguyen discovered that the KVM implementation for AMD processors in the Linux kernel with Secure Encrypted Virtualization (SEV) contained a race condition when accessing the GHCB page. A local attacker in a SEV guest VM could possibly use this to cause a denial of service (host system crash). (CVE-2023-4155) It was discovered that the TUN/TAP driver in the Linux kernel did not properly initialize socket data. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-4194) Maxim Suhanov discovered that the exFAT file system implementation in the Linux kernel did not properly check a file name length, leading to an out- of-bounds write vulnerability. An attacker could use this to construct a malicious exFAT image that, when mounted and operated on, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-4273)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1006-starfiveto a version that resolves this vulnerability.Fixed in 6.2.0-1006.7 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1013-awsto a version that resolves this vulnerability.Fixed in 6.2.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1013-oracleto a version that resolves this vulnerability.Fixed in 6.2.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-azureto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-kvmto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-raspito a version that resolves this vulnerability.Fixed in 6.2.0-1014.16 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1016-gcpto a version that resolves this vulnerability.Fixed in 6.2.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-genericto a version that resolves this vulnerability.Fixed in 6.2.0-34.34 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0-34.34 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0-34.34 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 6.2.0.1013.14 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 6.2.0.1016.16 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 6.2.0.34.34 - Upgrade
Upgrade
ubuntu/linux-image-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0.34.34 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0.34.34 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 6.2.0.1013.13 - Upgrade
Upgrade
ubuntu/linux-image-raspito a version that resolves this vulnerability.Fixed in 6.2.0.1014.17 - Upgrade
Upgrade
ubuntu/linux-image-raspi-nolpaeto a version that resolves this vulnerability.Fixed in 6.2.0.1014.17 - Upgrade
Upgrade
ubuntu/linux-image-starfiveto a version that resolves this vulnerability.Fixed in 6.2.0.1006.9 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 6.2.0.34.34 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1013-awsto a version that resolves this vulnerability.Fixed in 6.2.0-1013.13~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-azureto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-azure-fdeto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14~22.04.1.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1014-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0-1014.14~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1016-gcpto a version that resolves this vulnerability.Fixed in 6.2.0-1016.18~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-genericto a version that resolves this vulnerability.Fixed in 6.2.0-34.34~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0-34.34~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-34-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0-34.34~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 6.2.0.1013.13~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-azure-fdeto a version that resolves this vulnerability.Fixed in 6.2.0.1014.14~22.04.1.11 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 6.2.0.1016.18~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-generic-64k-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.34.34~22.04.11 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.34.34~22.04.11 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpae-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.34.34~22.04.11 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-64k-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.1014.14~22.04.11 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.1014.14~22.04.11 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.34.34~22.04.11
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-6412-1?
The USN-6412-1 vulnerability is classified as a high severity issue due to the potential for denial of service and arbitrary code execution.
How do I fix USN-6412-1?
To fix USN-6412-1, upgrade the affected Linux kernel packages to the specified versions in the advisory.
Which Ubuntu versions are affected by USN-6412-1?
USN-6412-1 affects Ubuntu 23.04 and older versions that use the vulnerable Linux kernel packages.
What type of vulnerability is described in USN-6412-1?
USN-6412-1 describes a use-after-free vulnerability caused by a race condition in the DVB Core driver.
Is physical access required for exploiting USN-6412-1?
Yes, a physically proximate attacker is required to exploit the USN-6412-1 vulnerability.