Bluetooth: ISO: lock sk in iso_connect_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.9, 6.12.114, 6.18.44, 7.1.8
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: lock sk in iso_connect_ind Accessing iso_pi(sk)->conn requires lock_sock, which is not taken in the "ev3" part of iso_connect_ind. It may also be NULL if socket has transitioned away from the LISTEN/CONNECT states before locking. Fix by adding lock/release. Recheck hcon is valid after lock acquire where needed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 168d9bf9c7f01df71e6404cfff66d9c2a8e968fb · fixed in 0e830354c120954ccb9ca15880245912722c4031; From 168d9bf9c7f01df71e6404cfff66d9c2a8e968fb · fixed in e8e9cff6d80eeec28dec4cf7cc18662986945391; From 168d9bf9c7f01df71e6404cfff66d9c2a8e968fb · fixed in 9bee7e476534f27e830658dad962d85da9edf6bf; From 168d9bf9c7f01df71e6404cfff66d9c2a8e968fb · fixed in 4311fd6f429065a8ba208660360a895627a00cf3; From 6.8.9 · fixed in 6.9
- Linux Linux
6.9
- KernelLinux
From 6.9.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8