System crash via uninitialized CAN device pointer
Published Oct 21, 2024 · Updated May 23, 2026
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system via CAN frames on TUN or bonding devices. The AF_CAN receive handlers trust an ARPHRD_CAN device type and dereference ml_priv without confirming that the CAN-private pointer was initialized. Local access is required; successful triggering causes an availability-only system crash without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system via CAN frames on TUN or bonding devices. The AF_CAN receive handlers trust an ARPHRD_CAN device type and dereference ml_priv without confirming that the CAN-private pointer was initialized. Local access is required; successful triggering causes an availability-only system crash without reported data disclosure or modification.
The record
- CVE
- CVE-2022-48977
- Published
- Oct 21, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record 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=1a5751d58b14195f763b8c1d9ef33fb8a93e95e7 <c42221efb1159d6a3c89e96685ee38acdce86b6f
- Affected versionversion=4ac1feff6ea6495cbfd336f4438a6c6d140544a6 <3982652957e8d79ac32efcb725450580650a8644
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <0acc442309a0a1b01bcdaa135e56e6398a49439c
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <c142cba37de29f740a3852f01f59876af8ae462a
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <fcc63f2f7ee3038d53216edd0d8291e57c752557
- Affected versionversion=5.10.28 <5.10.159
- Affected versionversion=5.11.12 <5.12
- Affected versionversion=5.12
- Affected versionversion=5.4.110 <5.4.227
- Affected versionversion=96340078d50a54f6a1252c62596bc44321c8bff9
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.
Public exploit references
- syzbot can_rcv_filter crash reproducerproof of concept · validated
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