Vulnerability · Published Jul 19, 2026 · Assigned by Linux

CVE-2026-63990bonding: refuse to enslave CAN devices

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 97.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: bonding: refuse to enslave CAN devices syzbot reported a kernel paging request crash in can_rx_unregister() inside net/can/af_can.c. The crash occurs because a virtual CAN device (vxcan) is being enslaved to a bonding master. During the enslavement process, 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. Since bonding does not initialize or maintain these CAN structures, subsequent operations on the half-enslaved interface (such as closing associated sockets via isotp_release) lead to a null-pointer dereference when accessing the CAN receiver lists. Bonding CAN interfaces is architecturally invalid as CAN lacks MAC addresses, ARP capabilities, and standard Ethernet link-layer mechanisms. While generic loopback devices are blocked globally in net/core/dev.c, virtual CAN devices bypass this check because they do not carry the IFF_LOOPBACK flag, despite acting as local software-loopbacks. Fix this by explicitly blocking network devices of type ARPHRD_CAN from being enslaved at the very beginning of bond_enslave(). This prevents illegal state mutations, eliminates the resulting KASAN crashes, and avoids potential memory leaks from incomplete socket cleanups. As the CAN support has been added a long time after bonding the Fixes-tag points to the introduction of ARPHRD_CAN that would have needed a specific handling in bonding_main.c.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.176-1DEBIAN-CVE-2026-63990
Debian:13linux6.12.94-1DEBIAN-CVE-2026-63990
Debian:14linux7.0.12-1DEBIAN-CVE-2026-63990
Ubuntu:22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux6.8.0-146.146UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-aws6.8.0-1066.69UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure6.8.0-1070.78UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1068.75UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gcp6.8.0-1070.78UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gke6.8.0-1065.73UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1051.55UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-ibm6.8.0-1066.67UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1066.67~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-kvm5.15.0-1109.114UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-195.205UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-146.146.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-146.146.1~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1112.113UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1064.67UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1064.67.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oracle5.15.0-1114.120UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oracle6.8.0-1063.66UBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-63990
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-146.146~22.04.1UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-63990
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-63990
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1080.84UBUNTU-CVE-2026-63990

Affected products (as reported)

VendorProductVersions
Linux Linux cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 69b78b5f3033272e53a2dc2dad675962654a5b38cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 41e8478c4cd896d3abbe33d41afc90c84ac66602cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before f4d78a81f57df82e9d82a2c07471fed1a1235893cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 02f1c87ded33b43d48b4a1d665da15f2157b30d8cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 9ea8a648d9120f7652bcde1ce2c4ad66871af707cd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 563090e5d450c665f70d955a39f9587afc7842ebcd05acfe65ed2cf2db683fa9a6adb8d35635263b – before 8ba68464e4787b6a7ec938826e16124df20fd23d
Linux Linux 2.6.25

References