Local kernel crash via double-freed transmit buffer
Published Apr 3, 2022 · Updated Aug 3, 2024
A double free in the Linux kernel through 5.17.1 allows local users to crash the system by triggering a failed MCBA USB CAN transmission. In mcba_usb_start_xmit, can_put_echo_skb consumes the original socket buffer, but the USB submission error path calls dev_kfree_skb on that buffer again while can_free_echo_skb releases its echo copy. Exploitation requires local access to transmit through the Microchip CAN BUS Analyzer driver and an error from usb_submit_urb; the bounded consequence is a kernel crash.
Summary
What happened
A double free in the Linux kernel through 5.17.1 allows local users to crash the system by triggering a failed MCBA USB CAN transmission. In mcba_usb_start_xmit, can_put_echo_skb consumes the original socket buffer, but the USB submission error path calls dev_kfree_skb on that buffer again while can_free_echo_skb releases its echo copy. Exploitation requires local access to transmit through the Microchip CAN BUS Analyzer driver and an error from usb_submit_urb; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2022-28389
- Published
- Apr 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 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.
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