Memory exhaustion via unreleased L2CAP start fragments
Published Oct 20, 2022 · Updated Apr 15, 2025
Resource leak in the Linux Kernel Bluetooth L2CAP stack allows attackers to exhaust kernel memory with malformed ACL start fragments. When a start fragment omits the L2CAP length, l2cap_recv_acldata copies its socket buffer into conn->rx_skb without releasing the original buffer. Reachability requires control of Bluetooth ACL input, and published assessments disagree on whether local privileges are required.
Summary
What happened
Resource leak in the Linux Kernel Bluetooth L2CAP stack allows attackers to exhaust kernel memory with malformed ACL start fragments. When a start fragment omits the L2CAP length, l2cap_recv_acldata copies its socket buffer into conn->rx_skb without releasing the original buffer. Reachability requires control of Bluetooth ACL input, and published assessments disagree on whether local privileges are required.
The record
- CVE
- CVE-2022-3619
- Published
- Oct 20, 2022
- Updated
- Apr 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, CWE-404, T1499.001
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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
- syzbot vhci_write C reproducerproof of concept · demonstrated
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