CVE-2024-42137: Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot
Commit 272970be3dab ("Bluetooth: hciqca: Fix driver shutdown on closed serdev") will cause below regression issue:
BT can't be enabled after below steps: cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure if property enable-gpios is not configured within DT|ACPI for QCA6390.
The commit is to fix a use-after-free issue within qcaserdevshutdown() by adding condition to avoid the serdev is flushed or wrote after closed but also introduces this regression issue regarding above steps since the VSC is not sent to reset controller during warm reboot.
Fixed by sending the VSC to reset controller within qcaserdevshutdown() once BT was ever enabled, and the use-after-free issue is also fixed by this change since the serdev is still opened before it is flushed or wrote.
Verified by the reported machine Dell XPS 13 9310 laptop over below two kernel commits: commit e00fc2700a3f ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of bluetooth-next tree. commit b23d98d46d28 ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of linus mainline tree.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-42137?
CVE-2024-42137 has been categorized with a severity that may impact Bluetooth functionality in affected Linux kernel versions.
How do I fix CVE-2024-42137?
To address CVE-2024-42137, update the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.119-1, or any higher patched version.
Which Linux kernel versions are affected by CVE-2024-42137?
CVE-2024-42137 affects Linux kernel versions between 5.10.165 and 5.10.222, 5.15.90 to 5.15.163, 6.1.8 to 6.1.98, 6.2 to 6.6.39, 6.7 to 6.9.9, and specific 6.10 release candidates.
What is the impact of CVE-2024-42137?
CVE-2024-42137 may prevent Bluetooth functionality from being enabled on devices using affected Linux kernel versions.
Is there a workaround for CVE-2024-42137?
There are no known workarounds for CVE-2024-42137, so updating to a fixed kernel version is essential.