Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN
- 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.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, and 3 more
- 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: reject accept queue add unless BT_LISTEN New sk should not be added to parent socket accept queue after last l2cap_sock_cleanup_listen() has run in l2cap_sock_teardown_cb() and state set to BT_CLOSED, as that can result to UAF on dereferencing the dangling parent reference. l2cap_sock_new_connection_cb() may race with parent l2cap_chan teardown, due to chan->state accessed without consistent locking: [Task 1] [Task 2] l2cap_sock_release(parent) l2cap_connect l2cap_sock_shutdown pchan = l2cap_global_chan_by_psm l2cap_chan_lock(pchan) l2cap_chan_close l2cap_sock_teardown_cb pchan->state = BT_CLOSED l2cap_chan_unlock(pchan) ------> l2cap_chan_lock(pchan) l2cap_new_connection l2cap_sock_new_connection_cb l2cap_chan_lock(pchan) <-------- l2cap_chan_unlock(pchan) l2cap_sock_kill(parent) /* bt_sk(sk)->parent dangling */ Fix by adding check for sk_state == BT_LISTEN after acquiring sk lock in l2cap_sock_new_connection_cb(). Add lock_sock() around sk_state writes where missing, to avoid data races. Although the data races on pchan->state should be fixed too, this defensive sk_state check probably makes sense in any case.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0c17c8832562b2aac288e89cefd0f46074f54bcb · fixed in bf61a65c6093970e3b50031c4b79ebf3bd411eba; From 5105f3e6b2df619c635b5f6a49fac131a36c7952 · fixed in 491e4c60017969b053888029998d2a61f298986a; From c88c185ae0a1067823661b220aeea613df2c127b · fixed in 2a3a27aaf19bf069720e024ce6fde54e6bf80df9; From 1810e42ff6716f320c7269d5850eca48b07b7427 · fixed in 87276dc15b559d32757a43b4415c8445fbae06c4; From 2ff1a41a912de8517b4482e946dd951b7d80edbf · fixed in c47339e169bf4a0a4cfabb91351471f67744c2bc; From 2ff1a41a912de8517b4482e946dd951b7d80edbf · fixed in d4bfa78fd67929b62b02013c107973e0c5b7aa9a; From 6.1.175 · fixed in 6.1.188; From 6.6.140 · fixed in 6.6.157; From 6.12.88 · fixed in 6.12.110; From 6.18.30 · fixed in 6.18.52; From 5.10.258 · fixed in 5.11; From 5.15.209 · fixed in 5.16; From 7.0.7 · fixed in 7.1
- Linux Linux
7.1
- KernelLinux
fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6