System crash via L2CAP receive race
Published Oct 17, 2022 · Updated Aug 3, 2024
Use-after-free in the Linux Kernel Bluetooth L2CAP subsystem allows local users to crash the system through a receive race. One flow queues an SKB while another dequeues and frees it; callers then access l2cap_ctrl data retained inside the freed buffer after l2cap_reassemble_sdu returns. Reachability requires local low-privileged access to exercise Bluetooth L2CAP receive paths, and the confirmed consequence is a system crash.
Summary
What happened
Use-after-free in the Linux Kernel Bluetooth L2CAP subsystem allows local users to crash the system through a receive race. One flow queues an SKB while another dequeues and frees it; callers then access l2cap_ctrl data retained inside the freed buffer after l2cap_reassemble_sdu returns. Reachability requires local low-privileged access to exercise Bluetooth L2CAP receive paths, and the confirmed consequence is a system crash.
The record
- CVE
- CVE-2022-3564
- Published
- Oct 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-119, CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo