Kernel crash via writable usbmon memory mappings
Published Oct 26, 2022 · Updated May 7, 2025
Memory corruption in Linux kernel usbmon before 5.19.15 and 6.0 allows local users to crash the kernel through a writable mapping. The mon_bin_mmap function accepted writable mappings of /dev/usbmon ring memory, allowing mapped user-space data to overwrite monitor internals. Opening and mapping /dev/usbmon requires elevated local privileges; corrupted ring data can trigger segfaults and use-after-free conditions.
Summary
What happened
Memory corruption in Linux kernel usbmon before 5.19.15 and 6.0 allows local users to crash the kernel through a writable mapping. The mon_bin_mmap function accepted writable mappings of /dev/usbmon ring memory, allowing mapped user-space data to overwrite monitor internals. Opening and mapping /dev/usbmon requires elevated local privileges; corrupted ring data can trigger segfaults and use-after-free conditions.
The record
- CVE
- CVE-2022-43750
- Published
- Oct 26, 2022
- Updated
- May 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 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?
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
- syzbot usbmon writable-mapping 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