Skip to main content
VulnerabilityPublished

CVE-2026-99673: Linux kernel · can: replace ARPHRD_CAN type checks with can_get_ml_priv()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f4910431fdf7b2800f0bec9f161900511f9a8bcd : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f4910431fdf7b2800f0bec9f161900511f9a8bcd, c693cbfbc2ad5ab159c671c58f285aa3d4d8a98b, 962947b69589881167054bae5accc8abfd5aa4b6 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.4.110 <5.5
  • >=5.10.28 <5.11
  • >=5.11.12 <5.12
Fixed in
  • f4910431fdf7b2800f0bec9f161900511f9a8bcd
  • c693cbfbc2ad5ab159c671c58f285aa3d4d8a98b
  • 962947b69589881167054bae5accc8abfd5aa4b6
  • 27edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab19
  • 5.12
  • 5.11
  • 5.5
LinuxLinuxAffected
  • =5.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: can: replace ARPHRD_CAN type checks with can_get_ml_priv() Commit 4e096a18867a ("net: introduce CAN specific pointer in the struct net_device") introduced an explicit way to assign the midlayer private pointer (dev->ml_priv) to named users like ML_PRIV_CAN. A valid pointer returned by can_get_ml_priv() therefore identifies a real CAN device. The referenced commit only converted the j1939 and proc code to this check, while the other parts of the CAN subsystem still rely on dev->type == ARPHRD_CAN. The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware type to ARPHRD_CAN while dev->ml_priv remains NULL. Such a repurposed netdevice passes the ARPHRD_CAN checks. Commit 8aa59e355949 ("can: af_can: fix NULL pointer dereference in can_rx_register()") already made can_rx_register() reject such devices. But can_rx_unregister() still only checks dev->type and dereferences the NULL ml_priv when it walks the receive lists of the device. CAN_ISOTP reaches this path: isotp_bind() ignores the return values of can_rx_register() and binds the socket anyway. When the socket is released or the device is unregistered, isotp_release() and isotp_notify() remove the filters that have never been registered and trigger the NULL pointer dereference in can_rx_unregister(). This only requires owning a TUN/TAP device or CAP_NET_ADMIN in an unprivileged user namespace. Convert the remaining ARPHRD_CAN checks in af_can, bcm, gw, isotp and raw to can_get_ml_priv().

References

Community reviews

Loading reviews…