CVE-2024-56605
Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
- 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
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() bt_sock_alloc() allocates the sk object and attaches it to the provided sock object. On error l2cap_sock_alloc() frees the sk object, but the dangling pointer is still attached to the sock object, which may create use-after-free in other code.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.6
References 7
git.kernel.org
- stable/c/f6ad641646b67f29c7578dcd6c25813c7dcbf51e
- stable/c/daa13175a6dea312a76099066cb4cbd4fc959a84
- stable/c/a8677028dd5123e5e525b8195483994d87123de4
- stable/c/bb2f2342a6ddf7c04f9aefbbfe86104cd138e629
- stable/c/8ad09ddc63ace3950ac43db6fbfe25b40f589dd6
- stable/c/61686abc2f3c2c67822aa23ce6f160467ec83d35
- stable/c/7c4f78cdb8e7501e9f92d291a7d956591bf73be9