USN-6896-2: Linux kernel vulnerabilities
It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270) It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042) Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099) Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307) It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when modifying certain settings values through debugfs. A privileged local attacker could use this to cause a denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859) Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861) Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-5.4.0-1127-oracleto a version that resolves this vulnerability.Fixed in 5.4.0-1127.136~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.4.0-189-genericto a version that resolves this vulnerability.Fixed in 5.4.0-189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.4.0-189-lowlatencyto a version that resolves this vulnerability.Fixed in 5.4.0-189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-oemto a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-oem-osp1to a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 5.4.0.1127.136~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-snapdragon-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.4.0.189.209~18.04.1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch USN-6896-2
Event History
Child vulnerabilities
Contains the following vulnerabilities.
- CVE-2024-24861
- CVE-2024-25739
- CVE-2024-26810
- CVE-2022-48627
- CVE-2024-27028
- CVE-2024-35910
- CVE-2024-26651
- CVE-2024-35935
- CVE-2024-26855
- CVE-2023-7042
- CVE-2024-26922
- CVE-2024-26994
- CVE-2024-35813
- CVE-2024-35853
- CVE-2024-35893
- CVE-2024-36006
- CVE-2024-35922
- CVE-2024-27074
- CVE-2024-26642
- CVE-2024-26828
- CVE-2024-35933
- CVE-2024-35789
- CVE-2024-27020
- CVE-2024-35852
- CVE-2024-27073
- CVE-2024-27000
- CVE-2024-35815
- CVE-2024-36004
- CVE-2024-26820
- CVE-2024-26857
- CVE-2024-26812
- CVE-2024-27076
- CVE-2024-35944
- CVE-2024-26935
- CVE-2023-52656
- CVE-2024-36020
- CVE-2024-27046
- CVE-2024-27013
- CVE-2024-35955
- CVE-2024-35930
- CVE-2024-24857
- CVE-2024-26903
- CVE-2024-35823
- CVE-2024-35900
- CVE-2024-27053
- CVE-2024-27419
- CVE-2023-52699
- CVE-2024-26974
- CVE-2024-26955
- CVE-2024-27043
- CVE-2024-35822
- CVE-2024-26926
- CVE-2024-26976
- CVE-2024-27388
- CVE-2024-26937
- CVE-2024-27078
- CVE-2024-35899
- CVE-2024-35830
- CVE-2024-35828
- CVE-2024-26894
- CVE-2024-27395
- CVE-2024-24858
- CVE-2024-22099
- CVE-2024-35847
- CVE-2023-52644
- CVE-2024-26931
- CVE-2024-26851
- CVE-2024-26882
- CVE-2024-35888
- CVE-2024-27436
- CVE-2024-35978
- CVE-2024-27437
- CVE-2024-35973
- CVE-2024-35950
- CVE-2024-26884
- CVE-2024-26966
- CVE-2024-26969
- CVE-2024-35819
- CVE-2024-26973
- CVE-2024-26874
- CVE-2024-27059
- CVE-2024-26862
- CVE-2024-35849
- CVE-2024-27030
- CVE-2024-35855
- CVE-2024-35969
- CVE-2024-27004
- CVE-2024-26999
- CVE-2024-26923
- CVE-2024-26852
- CVE-2024-26957
- CVE-2024-35877
- CVE-2024-27396
- CVE-2024-26901
- CVE-2024-35806
- CVE-2024-35898
- CVE-2024-35895
- CVE-2024-35809
- CVE-2024-35854
- CVE-2024-27077
- CVE-2024-26863
- CVE-2024-24859
- CVE-2023-6270
- CVE-2024-26898
- CVE-2024-26586
- CVE-2024-26687
- CVE-2024-27024
- CVE-2024-26965
- CVE-2024-35821
- CVE-2024-26993
- CVE-2024-26817
- CVE-2024-26984
- CVE-2024-35825
- CVE-2024-35960
- CVE-2023-52650
- CVE-2024-35925
- CVE-2024-36007
- CVE-2024-26956
- CVE-2024-27065
- CVE-2024-27044
- CVE-2024-26981
- CVE-2024-35897
- CVE-2024-35997
- CVE-2024-26934
- CVE-2024-27075
- CVE-2024-35984
- CVE-2024-27001
- CVE-2024-23307
- CVE-2024-26883
- CVE-2024-35805
- CVE-2024-26813
- CVE-2023-52880
- CVE-2024-26889
- CVE-2024-35936
- CVE-2024-35886
- CVE-2024-26875
- CVE-2024-26880
- CVE-2024-27038
- CVE-2024-35915
- CVE-2024-26859
- CVE-2024-35807
- CVE-2023-52620
- CVE-2024-26654
- CVE-2024-35982
- CVE-2024-26816
- CVE-2024-27008
- CVE-2024-26878
Frequently Asked Questions
What is the severity of USN-6896-2?
The severity of USN-6896-2 is critical due to its potential for denial of service and arbitrary code execution through a use-after-free vulnerability.
How do I fix USN-6896-2?
To fix USN-6896-2, update your system to the latest kernel version specifically remediated for Ubuntu 18.04.
What systems are affected by USN-6896-2?
USN-6896-2 affects Ubuntu 18.04 systems running specific versions of the Linux kernel, including various image packages like linux-image-5.4.0-1127-oracle and linux-image-5.4.0-189-generic.
Can an attacker exploit the USN-6896-2 vulnerability?
Yes, an attacker can exploit the USN-6896-2 vulnerability to create a denial of service or potentially execute arbitrary code against vulnerable systems.
Is there a known exploit for USN-6896-2?
As of now, there are no publicly disclosed exploits specifically targeting the USN-6896-2 vulnerability.