Kernel crash via invalid CAN device bonding
Published Jul 19, 2026 · Updated Jul 19, 2026
NULL-pointer dereference in Linux Kernel bonding allows local users to crash the kernel by enslaving a virtual CAN interface. The bond_enslave() path accepts ARPHRD_CAN devices and applies Ethernet-oriented state changes without maintaining can_ml_priv, causing can_rx_unregister() to dereference a null receiver-list pointer during later socket cleanup. Reachability requires local control over network-device configuration and a virtual CAN interface; successful triggering interrupts the host.
Summary
What happened
NULL-pointer dereference in Linux Kernel bonding allows local users to crash the kernel by enslaving a virtual CAN interface. The bond_enslave() path accepts ARPHRD_CAN devices and applies Ethernet-oriented state changes without maintaining can_ml_priv, causing can_rx_unregister() to dereference a null receiver-list pointer during later socket cleanup. Reachability requires local control over network-device configuration and a virtual CAN interface; successful triggering interrupts the host.
The record
- CVE
- CVE-2026-63990
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=2.6.25
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <02f1c87ded33b43d48b4a1d665da15f2157b30d8
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <41e8478c4cd896d3abbe33d41afc90c84ac66602
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <563090e5d450c665f70d955a39f9587afc7842eb
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <69b78b5f3033272e53a2dc2dad675962654a5b38
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <8ba68464e4787b6a7ec938826e16124df20fd23d
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <9ea8a648d9120f7652bcde1ce2c4ad66871af707
- Affected versionversion=cd05acfe65ed2cf2db683fa9a6adb8d35635263b <f4d78a81f57df82e9d82a2c07471fed1a1235893
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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