Skip to main content
VulnerabilityPublished

CVE-2026-99674: Linux kernel · can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99674· High

Not known to be exploited : upgrade to 2de9c3df452e159f82ef14ca497e5be407c66493 or 0fce44e29fce4b07642491b098afb41bd571e4f2 soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2de9c3df452e159f82ef14ca497e5be407c66493, 0fce44e29fce4b07642491b098afb41bd571e4f2

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 Linux kernel to 2de9c3df452e159f82ef14ca497e5be407c66493 or 0fce44e29fce4b07642491b098afb41bd571e4f2.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fb08cba12b52cba4366e858932307649dc5304e2, < 2de9c3df452e159f82ef14ca497e5be407c66493
Fixed in
  • 2de9c3df452e159f82ef14ca497e5be407c66493
LinuxLinuxAffected
  • ≥ fb08cba12b52cba4366e858932307649dc5304e2, < 0fce44e29fce4b07642491b098afb41bd571e4f2
Fixed in
  • 0fce44e29fce4b07642491b098afb41bd571e4f2
LinuxLinuxAffected
  • =6.1
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices Sending a PF_PACKET bypasses the CAN framework logic and can directly reach a CAN driver's xmit() function. The PF_PACKET framework only checks that skb->len does not exceed the net_device MTU. For a CAN device that is not CAN XL capable, anything above CANFD_MTU (72 bytes) is therefore dropped before it reaches the driver. However, CAN XL frames are variable length. can_is_canxl_skb() accepts lengths in the range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to 2060 bytes. As a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes can pass both the MTU and the can_dropped_invalid_skb() checks. A driver that does not support CAN XL will interpret canxl_frame->flags as a length because of the overlap with can_frame->len. And because CANXL_XLF is set, the resulting length is between 128 and 255. For drivers that do not check can_frame->len before copying can_frame->data, as most drivers do, this results in a buffer overflow of up to 247 bytes. Drop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL capability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.

References

Community reviews

Loading reviews…