{"api_version":"1","generated_at":"2026-11-22T20:39:58+00:00","cve":"CVE-2026-99674","urls":{"html":"https://cve.report/CVE-2026-99674","api":"https://cve.report/api/cve/CVE-2026-99674.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99674","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99674"},"summary":{"title":"can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices","description":"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->len 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->flags\nas a length because of the overlap with can_frame->len. And because\nCANXL_XLF is set, the resulting length is between 128 and 255. For\ndrivers that do not check can_frame->len before copying can_frame->data,\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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:02","updated_at":"2026-11-22 11:17:05"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/2de9c3df452e159f82ef14ca497e5be407c66493","name":"https://git.kernel.org/stable/c/2de9c3df452e159f82ef14ca497e5be407c66493","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0fce44e29fce4b07642491b098afb41bd571e4f2","name":"https://git.kernel.org/stable/c/0fce44e29fce4b07642491b098afb41bd571e4f2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99674","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99674","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fb08cba12b52cba4366e858932307649dc5304e2 2de9c3df452e159f82ef14ca497e5be407c66493 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fb08cba12b52cba4366e858932307649dc5304e2 0fce44e29fce4b07642491b098afb41bd571e4f2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"99674","cve":"CVE-2026-99674","epss":"0.001960000","percentile":"0.092790000","score_date":"2026-11-21","updated_at":"2026-11-22 00:14:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/can/dev/skb.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2de9c3df452e159f82ef14ca497e5be407c66493","status":"affected","version":"fb08cba12b52cba4366e858932307649dc5304e2","versionType":"git"},{"lessThan":"0fce44e29fce4b07642491b098afb41bd571e4f2","status":"affected","version":"fb08cba12b52cba4366e858932307649dc5304e2","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/can/dev/skb.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.1"},{"lessThan":"6.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->len 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->flags\nas a length because of the overlap with can_frame->len. And because\nCANXL_XLF is set, the resulting length is between 128 and 255. For\ndrivers that do not check can_frame->len before copying can_frame->data,\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."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The bad bytes are a local TX_SEND payload copied in bcm_tx_send() (or a PF_PACKET buffer in packet_snd()), not a frame read off the CAN wire. can_send() sets skb->protocol to ETH_P_CANXL and dev_queue_xmit() reaches ndo_start_xmit, which calls can_dropped_invalid_skb().\nAC:L - The sender sets canxl_frame.flags with CANXL_XLF and the u16 at canxl_frame.len so a 16-byte skb (72 bytes if the device MTU is CANFD_MTU) passes can_is_canxl_skb() and the MTU check. The driver then uses that flags byte as can_frame.len with no race or hardware fault required.\nPR:L - can_create() and bcm_connect() do not call capable(). An unprivileged user can socket(PF_CAN, SOCK_DGRAM, CAN_BCM), connect to an up non-XL CAN netdev, and TX_SEND; bcm_tx_send() calls can_send() and skips raw_check_txframe()'s CAN_CAP_XL rejection. CAP_NET_RAW is not required.\nUI:N - The attacker connects their own BCM socket and issues TX_SEND. No other user must mount media or confirm a prompt; an already-up CAN interface is the operating state of the controller, not a victim action.\nS:U - The overflow stays in the kernel that owns the CAN netdev: softing_netdev_start_xmit() smashes a stack buffer, and gs_can_start_xmit() and usb_8dev_start_xmit() overflow kmalloc or DMA objects. That is host kernel memory corruption, not a guest-to-host or IOMMU crossing.\nC:H - cf->len is canxl_frame.flags (128–255) while the skb from bcm_tx_send() is only CAN_MTU (16) or CANFD_MTU (72). gs_can_start_xmit() and usb_8dev_start_xmit() memcpy that many bytes from cf->data, reading skb tailroom and skb_shared_info into the overflowed object.\nI:H - can_dropped_invalid_skb() accepts the ETH_P_CANXL skb when CAN_CAP_XL is absent. usb_8dev_start_xmit() then memcpy()s cf->len bytes into usb_8dev_tx_msg.data[8] inside a 16-byte buffer, gs_can_start_xmit() into classic_can.data[8], and softing_netdev_start_xmit() into a 16-byte stack buf.\nA:H - The same copy runs off the skb and the fixed 8-byte or 16-byte destination and oopses or panics the kernel. sja1000_start_xmit() also does for (i = 0; i < cf->len; i++) priv->write_reg(), writing past the 8-byte TX mailbox."}]}],"providerMetadata":{"dateUpdated":"2026-11-22T11:09:36.786Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2de9c3df452e159f82ef14ca497e5be407c66493"},{"url":"https://git.kernel.org/stable/c/0fce44e29fce4b07642491b098afb41bd571e4f2"}],"title":"can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99674","datePublished":"2026-11-20T05:50:22.677Z","dateReserved":"2026-09-25T10:25:14.428Z","dateUpdated":"2026-11-22T11:09:36.786Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:02","lastModifiedDate":"2026-11-22 11:17:05","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99674","Ordinal":"1","Title":"can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN","CVE":"CVE-2026-99674","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99674","Ordinal":"1","NoteData":"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->len 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->flags\nas a length because of the overlap with can_frame->len. And because\nCANXL_XLF is set, the resulting length is between 128 and 255. For\ndrivers that do not check can_frame->len before copying can_frame->data,\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.","Type":"Description","Title":"can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN"}]}}}