Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.14, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -> hci_proto_disconn_ind -> l2cap_disconn_ind. This is UAF if the l2cap_conn is deleted concurrently. disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work. Fix by using proto_lock to guard l2cap_data, in addition to hdev->lock which is held in other access paths.
Timeline
- CVE published34 days
- Record last updated
Affected versions
- Linux Linux
From efc30877bd4bc85fefe98d80af60fafc86e5775e · fixed in 0fa448369c87e20b2aeaeaca0187d698dd61f791; From f87271d21dd4ee83857ca11b94e7b4952749bbae · fixed in 7c032b6d48a46634cbd58aaebad2638c00ad3b51; From ab4eedb790cae44313759b50fe47da285e2519d5 · fixed in b495a3a9b33bc4e4613e685bf5c96c136caa22d8; From ab4eedb790cae44313759b50fe47da285e2519d5 · fixed in 2b66c83ff1751d6bd3201b3017206262ab46dc05; From 6.6.84 · fixed in 6.6.160; From 6.12.20 · fixed in 6.12.114; From 6.13.8 · fixed in 6.14
- Linux Linux
6.14
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 7.2.6