Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7c032b6d48a46634cbd58aaebad2638c00ad3b51, Kernel 6.6.160, Kernel 2b66c83ff1751d6bd3201b3017206262ab46dc05 and 5 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f87271d21dd4ee83857ca11b94e7b4952749bbae <7c032b6d48a46634cbd58aaebad2638c00ad3b51, >=6.6.84 <6.6.160, >=ab4eedb790cae44313759b50fe47da285e2519d5 <2b66c83ff1751d6bd3201b3017206262ab46dc05, >=ab4eedb790cae44313759b50fe47da285e2519d5 <b495a3a9b33bc4e4613e685bf5c96c136caa22d8, >=efc30877bd4bc85fefe98d80af60fafc86e5775e <0fa448369c87e20b2aeaeaca0187d698dd61f791, =18ab6b6078fa8191ca30a3065d57bf35d5635761, =6.14, >=6.12.20 <6.12.114, >=6.13.8 <6.14 | 7c032b6d48a46634cbd58aaebad2638c00ad3b51, 6.6.160, 2b66c83ff1751d6bd3201b3017206262ab46dc05, b495a3a9b33bc4e4613e685bf5c96c136caa22d8, 0fa448369c87e20b2aeaeaca0187d698dd61f791, 6.12.114, 6.14 |
| linux-kernel: Kernel | >=6.13.8 <6.14, >=6.14.0 <7.2.6, >=6.6.84 <6.6.160, >=6.12.20 <6.12.114 | 6.14, 7.2.6, 6.6.160, 6.12.114 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket