{"id":"AZL-115492","summary":"CVE-2026-99674 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices\n\nSending a PF_PACKET bypasses the CAN framework logic and can directly\nreach a CAN driver's xmit() function. The PF_PACKET framework only\nchecks that skb-\u003elen does not exceed the net_device MTU.\n\nFor a CAN device that is not CAN XL capable, anything above CANFD_MTU\n(72 bytes) is therefore dropped before it reaches the driver. However,\nCAN XL frames are variable length. can_is_canxl_skb() accepts lengths in\nthe range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to\n2060 bytes.\n\nAs a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes\ncan pass both the MTU and the can_dropped_invalid_skb() checks.\n\nA driver that does not support CAN XL will interpret canxl_frame-\u003eflags\nas a length because of the overlap with can_frame-\u003elen. And because\nCANXL_XLF is set, the resulting length is between 128 and 255. For\ndrivers that do not check can_frame-\u003elen before copying can_frame-\u003edata,\nas most drivers do, this results in a buffer overflow of up to 247\nbytes.\n\nDrop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL\ncapability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.","modified":"2026-11-21T14:17:23.961101421Z","published":"2026-11-20T06:18:02Z","upstream":["CVE-2026-99674"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99674"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115492.json"}}],"schema_version":"1.9.2"}