Local system crash via transmit-path double free
Published Apr 3, 2022 · Updated May 5, 2025
A double free in the Linux kernel through 5.17.1 allows local users to crash the system through the 8 Devices USB2CAN transmit path. When usb_submit_urb() fails, usb_8dev_start_xmit() performs cleanup that frees a socket buffer already released by the CAN echo-buffer functions. The affected path requires local low-privileged access and use of the 8 Devices USB2CAN interface, and the documented consequence is a system crash.
Summary
What happened
A double free in the Linux kernel through 5.17.1 allows local users to crash the system through the 8 Devices USB2CAN transmit path. When usb_submit_urb() fails, usb_8dev_start_xmit() performs cleanup that frees a socket buffer already released by the CAN echo-buffer functions. The affected path requires local low-privileged access and use of the 8 Devices USB2CAN interface, and the documented consequence is a system crash.
The record
- CVE
- CVE-2022-28388
- Published
- Apr 3, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 3, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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.
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