Local denial of service via leaked socket buffers
Published Mar 11, 2022 · Updated Aug 3, 2024
Memory leak in Linux kernel 5.13 through 5.15.16 and 5.16 through 5.16.2 allows local users to exhaust memory using invalid Bluetooth frames. The virtbt_rx_handle function lacks a default packet-type case that frees the received socket buffer, so each invalid frame retains its allocation. The VirtIO Bluetooth driver must be active, and local users must have access to its VirtIO counterpart; repeated malformed frames can deny service.
Summary
What happened
Memory leak in Linux kernel 5.13 through 5.15.16 and 5.16 through 5.16.2 allows local users to exhaust memory using invalid Bluetooth frames. The virtbt_rx_handle function lacks a default packet-type case that frees the received socket buffer, so each invalid frame retains its allocation. The VirtIO Bluetooth driver must be active, and local users must have access to its VirtIO counterpart; repeated malformed frames can deny service.
The record
- CVE
- CVE-2022-26878
- Published
- Mar 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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