CVE-2026-63990 Linux CVE debrief

Who should care

Users of Linux kernel, particularly those who manage Linux-based systems and networks, should be aware of this vulnerability. They should review their system configurations to ensure that no CAN devices are being used in conjunction with bonding. Additionally, Linux kernel developers and maintainers should take note of this vulnerability and ensure that proper handling of CAN devices is implemented in the bonding driver.

Technical summary

The Linux kernel vulnerability occurs because the bonding driver does not properly handle CAN devices. When a virtual CAN device (vxcan) is enslaved to a bonding master, the bonding driver mutates and modifies the network device states to fit an Ethernet-like aggregation model. However, CAN devices operate on a completely different Layer 2 architecture, relying on the CAN mid-layer private data structure (can_ml_priv) instead of standard Ethernet structures. This leads to a null-pointer dereference when accessing the CAN receiver lists. The fix explicitly blocks network devices of type ARPHRD_CAN from being enslaved at the very beginning of bond_enslave(), preventing illegal state mutations and eliminating the resulting KASAN crashes.

Defensive priority

High

Recommended defensive actions

• Update Linux kernel to the latest version
• Disable bonding for CAN devices
• Monitor CAN device usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was reported by syzbot and has been resolved by explicitly blocking network devices of type ARPHRD_CAN from being enslaved at the very beginning of bond_enslave(). To verify, defenders should review the CAN device usage and ensure that no virtual CAN devices are being enslaved to a bonding master. Additionally, they should check for any potential memory leaks from incomplete socket cleanups and validate the affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.