In the Linux kernel, the following vulnerability has been resolved: bonding: refuse to enslave CAN devices syzbot reported a kernel paging request… (CVE-2026-63990)
A vulnerability in the Linux kernel bonding driver allowed virtual CAN devices to be enslaved to bonding masters, causing kernel paging request crashes due to null-pointer dereferences. This occurs because CAN devices use a different Layer 2 architecture than Ethernet devices, which bonding assumes. The issue was fixed by blocking CAN devices from being enslaved, preventing illegal state mutations and crashes.
AI Analysis
Technical Summary
The Linux kernel bonding driver improperly allowed CAN network devices, specifically virtual CAN devices (vxcan), to be enslaved to bonding masters. Bonding modifies network device states assuming Ethernet-like behavior, but CAN devices rely on a distinct CAN mid-layer private data structure. This mismatch leads to null-pointer dereferences and kernel crashes during operations like socket closure. The fix explicitly blocks devices of type ARPHRD_CAN from being enslaved in bond_enslave(), preventing these crashes and potential memory leaks.
Potential Impact
Exploiting this vulnerability can cause kernel paging request crashes (null-pointer dereferences) leading to system instability or denial of service. There is no indication of code execution or privilege escalation. The impact is limited to systems using bonding with CAN devices, which is architecturally invalid and now prevented.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that blocks CAN devices from being enslaved by the bonding driver. Users should update to a kernel version that includes this fix. Since this is a kernel-level fix, no additional mitigation is required once patched. Patch status is not explicitly stated here; check the vendor or Linux kernel advisory for the exact fixed version and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: bonding: refuse to enslave CAN devices syzbot reported a kernel paging request… (CVE-2026-63990)
Description
A vulnerability in the Linux kernel bonding driver allowed virtual CAN devices to be enslaved to bonding masters, causing kernel paging request crashes due to null-pointer dereferences. This occurs because CAN devices use a different Layer 2 architecture than Ethernet devices, which bonding assumes. The issue was fixed by blocking CAN devices from being enslaved, preventing illegal state mutations and crashes.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel bonding driver improperly allowed CAN network devices, specifically virtual CAN devices (vxcan), to be enslaved to bonding masters. Bonding modifies network device states assuming Ethernet-like behavior, but CAN devices rely on a distinct CAN mid-layer private data structure. This mismatch leads to null-pointer dereferences and kernel crashes during operations like socket closure. The fix explicitly blocks devices of type ARPHRD_CAN from being enslaved in bond_enslave(), preventing these crashes and potential memory leaks.
Potential Impact
Exploiting this vulnerability can cause kernel paging request crashes (null-pointer dereferences) leading to system instability or denial of service. There is no indication of code execution or privilege escalation. The impact is limited to systems using bonding with CAN devices, which is architecturally invalid and now prevented.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that blocks CAN devices from being enslaved by the bonding driver. Users should update to a kernel version that includes this fix. Since this is a kernel-level fix, no additional mitigation is required once patched. Patch status is not explicitly stated here; check the vendor or Linux kernel advisory for the exact fixed version and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vcmq-h7g2-2m6j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63990"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27aa2a4a8d598912dbb6
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 20:00:21 UTC
Last updated: 07/20/2026, 17:42:33 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.