PT-2026-152554
CVE-2026-99674
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾