CVE-2026-99033

net/packet: guard the ll header push in packet_rcv_spkt()

Description

In the Linux kernel, the following vulnerability has been resolved: net/packet: guard the ll header push in packet_rcv_spkt() packet_rcv_spkt() restores the link layer header with skb_push(skb, skb->data - skb_mac_header(skb)); That subtraction is only meaningful when the device actually has a link layer header. packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not. commit d549699048b4 ("net/packet: fix packet receive on L3 devices without visible hard header") introduced the helper and changed the two call sites, and this one stayed behind. A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to. A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 ("can: remove private CAN skb headroom infrastructure") dropped the skb_reset_*_header() calls that used to be there. skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0: skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0 kernel BUG at net/core/skbuff.c:214! RIP: 0010:skb_panic+0x50/0x60 Call Trace: <IRQ> skb_push+0x38/0x40 packet_rcv_spkt+0xe1/0x170 __netif_receive_skb_core.constprop.0+0x7e8/0xd30 ... Kernel panic - not syncing: Fatal exception in interrupt The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface. The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic. Guard the push the way the other two receive paths do. Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out. One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally. Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.185% likely to be exploited in the next 30 days, higher than 8.188% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 48aa1155fa8d83362fc33d02d527a3c3fe40ce1c (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 7f84ed94ccfe36091234a2891b88356dc06e6d66 (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding b880df0e487caa85c3c7ffda37dcd05334b1aa80 (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding d8a24b9e1774a93943caf68d48c5e17be432220b (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 31c7b15b3716e8d0dad58d2c3cdf321dfd06f4be (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 3efe0e0944157fdd2072b4dc7eb0491a317ed272 (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 00fbf71e74115f7628fc0880b855434b1e70c40c (affected)
  • d549699048b4b5c22dd710455bcdb76966e55aa3 up to but excluding 28bc1ef699610ee09ce3d46a00552f5a0a0144bd (affected)
  • dadddde259a19105ee69e788835f4d4552767aa9 (affected)
  • 5.9.13 up to but excluding 5.10 (affected)
LinuxLinux
  • Default status: affected
  • 5.10 (affected)
  • 0 up to but excluding 5.10 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References