Kernel crash via CAN bond device binding
Published May 1, 2025 · Updated May 23, 2026
NULL pointer dereference in the AF_CAN subsystem of affected Linux kernel releases allows local users to crash the kernel through a crafted bind. can_rx_register() assigns dev_rcv_lists from an unallocated ml_priv pointer when a CAN raw socket is bound to a bond device backed by vxcan. Reaching the fault requires local low-privilege access to create and bind the required bond, vxcan, and CAN sockets; exploitation interrupts the host by triggering a kernel oops.
Summary
What happened
NULL pointer dereference in the AF_CAN subsystem of affected Linux kernel releases allows local users to crash the kernel through a crafted bind. can_rx_register() assigns dev_rcv_lists from an unallocated ml_priv pointer when a CAN raw socket is bound to a bond device backed by vxcan. Reaching the fault requires local low-privilege access to create and bind the required bond, vxcan, and CAN sockets; exploitation interrupts the host by triggering a kernel oops.
The record
- CVE
- CVE-2022-49863
- Published
- May 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE 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 <d68fa77ee3d03bad6fe84e89759ddf7005f9e9c6
- Affected versionversion=4ac1feff6ea6495cbfd336f4438a6c6d140544a6 <afab4655750fcb3fca359bc7d7214e3d634cdf9c
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <261178a1c2623077d62e374a75c195e6c99a6f05
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <8aa59e355949442c408408c2d836e561794c40a1
- Affected versionversion=4e096a18867a5a989b510f6999d9c6b6622e8f7b <a8055677b054bc2bb78beb1080fdc2dc5158c2fe
- Affected versionversion=5.10.28 <5.10.155
- Affected versionversion=5.11.12 <5.12
- Affected versionversion=5.12
- Affected versionversion=5.4.110 <5.4.225
- Affected versionversion=96340078d50a54f6a1252c62596bc44321c8bff9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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