Skip to content
Threat Brief

← All advisories

CVE-2026-99673

Severity unknownNo known exploitationFix available

can: replace ARPHRD_CAN type checks with can_get_ml_priv()

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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().

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 4e096a18867a5a989b510f6999d9c6b6622e8f7b before c693cbfbc2ad5ab159c671c58f285aa3d4d8a98bc693cbfbc2ad5ab159c671c58f285aa3d4d8a98bCVE Program
LinuxLinuxfrom 4e096a18867a5a989b510f6999d9c6b6622e8f7b before f4910431fdf7b2800f0bec9f161900511f9a8bcdf4910431fdf7b2800f0bec9f161900511f9a8bcdCVE Program
LinuxLinuxfrom 4e096a18867a5a989b510f6999d9c6b6622e8f7b before 27edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab1927edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab19CVE Program
LinuxLinuxfrom 4e096a18867a5a989b510f6999d9c6b6622e8f7b before 962947b69589881167054bae5accc8abfd5aa4b6962947b69589881167054bae5accc8abfd5aa4b6CVE Program
LinuxLinuxfrom 5.10.28 before 5.115.11CVE Program
LinuxLinuxfrom 5.11.12 before 5.125.12CVE Program
LinuxLinuxfrom 5.4.110 before 5.55.5CVE Program
LinuxLinux1a5751d58b14195f763b8c1d9ef33fb8a93e95e7Not documentedCVE Program
LinuxLinux4ac1feff6ea6495cbfd336f4438a6c6d140544a6Not documentedCVE Program
LinuxLinux5.12Not documentedCVE Program
LinuxLinux96340078d50a54f6a1252c62596bc44321c8bff9Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references