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

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

can: dev: candroppedinvalidskb: drop CAN XL frames on non-CAN XL devices

Sending a PFPACKET bypasses the CAN framework logic and can directly reach a CAN driver's xmit() function. The PFPACKET framework only checks that skb->len does not exceed the netdevice MTU.

For a CAN device that is not CAN XL capable, anything above CANFDMTU (72 bytes) is therefore dropped before it reaches the driver. However, CAN XL frames are variable length. caniscanxlskb() accepts lengths in the range CANXLHDRSIZE + CANXLMINDLEN up to CANXLMTU, i.e. 13 to 2060 bytes.

As a result, an ETHPCANXL skb with a length between 13 and 72 bytes can pass both the MTU and the candroppedinvalidskb() checks.

A driver that does not support CAN XL will interpret canxlframe->flags as a length because of the overlap with canframe->len. And because CANXLXLF is set, the resulting length is between 128 and 255. For drivers that do not check canframe->len before copying canframe->data, as most drivers do, this results in a buffer overflow of up to 247 bytes.

Drop ETHPCANXL skbs if the device does not have the CANCAPXL capability. Keep caniscanxlskb() for the validation of CAN XL skbs.

Affected Software

5 affected componentsFixes available
linux/kernel>=6.1.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  3. Compensating control

    Drop ETH_P_CANXL skbs when the CAN device does not have the CAN_CAP_XL capability.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems with CAN devices that do not support CAN XL are exposed when PF_PACKET traffic can directly reach the driver's transmit function. The overflow affects drivers that do not validate can_frame->len before copying can_frame->data, which the advisory says describes most drivers.

2

What does an attacker need to send to trigger the vulnerable path?

The attacker needs to send an ETH_P_CANXL PF_PACKET skb with a length between 13 and 72 bytes to a non-CAN-XL CAN device. This range passes both the device MTU check and the pre-fix CAN skb validation.

3

What is the potential impact at the driver level?

A non-CAN-XL driver can interpret CAN XL frame flags as a frame length between 128 and 255 bytes. Drivers that copy data without checking that length can overflow a buffer by up to 247 bytes.

4

What can be done if the fix cannot be deployed immediately?

Ensure that ETH_P_CANXL skbs are dropped for devices that lack the CAN_CAP_XL capability. This prevents CAN XL packets from reaching non-CAN-XL drivers through the affected path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203