Linux
Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= efc30877bd4bc85fefe98d80af60fafc86e5775e, < 0fa448369c87e20b2aeaeaca0187d698dd61f791
- >= f87271d21dd4ee83857ca11b94e7b4952749bbae, < 7c032b6d48a46634cbd58aaebad2638c00ad3b51
- >= ab4eedb790cae44313759b50fe47da285e2519d5, < b495a3a9b33bc4e4613e685bf5c96c136caa22d8
- >= ab4eedb790cae44313759b50fe47da285e2519d5, < 2b66c83ff1751d6bd3201b3017206262ab46dc05
- 18ab6b6078fa8191ca30a3065d57bf35d5635761
- >= 6.6.84, < 6.6.160
- >= 6.12.20, < 6.12.114
- >= 6.13.8, < 6.14
Fixed in 0fa448369c87e20b2aeaeaca0187d698dd61f791, 7c032b6d48a46634cbd58aaebad2638c00ad3b51, b495a3a9b33bc4e4613e685bf5c96c136caa22d8, 2b66c83ff1751d6bd3201b3017206262ab46dc05, 6.6.160, 6.12.114, 6.14
- 6.14
Fixed in 0, 6.6.160, 6.12.114, 7.2.6, 7.3
Mitigation
Upgrade Linux to 0fa448369c87e20b2aeaeaca0187d698dd61f791 or 7c032b6d48a46634cbd58aaebad2638c00ad3b51 or b495a3a9b33bc4e4613e685bf5c96c136caa22d8 or 2b66c83ff1751d6bd3201b3017206262ab46dc05 or 6.6.160 or 6.12.114 or 6.14 or later.
Upgrade Linux to 0 or 6.6.160 or 6.12.114 or 7.2.6 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.