Local system crash via CAN receive filtering
Published Apr 19, 2023 · Updated Feb 5, 2025
Null pointer dereference in Linux Kernel before 6.1-rc9 allows local users to crash the system through CAN frame reception. The can_rcv_filter path treats bonding or TUN devices claiming the CAN type as initialized CAN devices and dereferences an unset ml_priv pointer. Local access is required, and successful exploitation interrupts the entire host without reported data disclosure or modification.
Summary
What happened
Null pointer dereference in Linux Kernel before 6.1-rc9 allows local users to crash the system through CAN frame reception. The can_rcv_filter path treats bonding or TUN devices claiming the CAN type as initialized CAN devices and dereferences an unset ml_priv pointer. Local access is required, and successful exploitation interrupts the entire host without reported data disclosure or modification.
The record
- CVE
- CVE-2023-2166
- Published
- Apr 19, 2023
- Updated
- Feb 5, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2023CVE publishedPublication date reported by the CVE source.
- Feb 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Linux Kernel version prior to Kernel 6.1 RC9
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
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