CVE-2026-99033

Что произошло

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: 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.

Что делать

dpkg-query -W -f='${Package}	${Version}\n'

rpm -qa --qf '%{NAME}\t%{VERSION}-%{RELEASE}\n'

Get-HotFix | Select-Object HotFixID, InstalledOn

Продукты и затронутые версии

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "48aa1155fa8d83362fc33d02d527a3c3fe40ce1c",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "7f84ed94ccfe36091234a2891b88356dc06e6d66",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "b880df0e487caa85c3c7ffda37dcd05334b1aa80",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "d8a24b9e1774a93943caf68d48c5e17be432220b",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "31c7b15b3716e8d0dad58d2c3cdf321dfd06f4be",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "3efe0e0944157fdd2072b4dc7eb0491a317ed272",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "00fbf71e74115f7628fc0880b855434b1e70c40c",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "d549699048b4b5c22dd710455bcdb76966e55aa3",
  "lessThan": "28bc1ef699610ee09ce3d46a00552f5a0a0144bd",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "dadddde259a19105ee69e788835f4d4552767aa9",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "5.9.13",
  "lessThan": "5.10",
  "versionType": "semver"
}

{
  "status": "affected",
  "version": "5.10"
}

{
  "status": "unaffected",
  "version": "0",
  "lessThan": "5.10",
  "versionType": "semver"
}

{
  "status": "unaffected",
  "version": "5.10.273",
  "versionType": "semver",
  "lessThanOrEqual": "5.10.*"
}

{
  "status": "unaffected",
  "version": "5.15.224",
  "versionType": "semver",
  "lessThanOrEqual": "5.15.*"
}

{
  "status": "unaffected",
  "version": "6.1.191",
  "versionType": "semver",
  "lessThanOrEqual": "6.1.*"
}

{
  "status": "unaffected",
  "version": "6.6.160",
  "versionType": "semver",
  "lessThanOrEqual": "6.6.*"
}

{
  "status": "unaffected",
  "version": "6.12.113",
  "versionType": "semver",
  "lessThanOrEqual": "6.12.*"
}

{
  "status": "unaffected",
  "version": "6.18.57",
  "versionType": "semver",
  "lessThanOrEqual": "6.18.*"
}

{
  "status": "unaffected",
  "version": "7.2.11",
  "versionType": "semver",
  "lessThanOrEqual": "7.2.*"
}

{
  "status": "unaffected",
  "version": "7.3",
  "versionType": "original_commit_for_fix",
  "lessThanOrEqual": "*"
}

CVSS: оценки и векторы

Оценка CVSS отсутствует.

Источники и ссылки

{
  "cwes": [],
  "epss": {
    "source": "epss",
    "received_at": "2026-11-03T21:16:07.982913+00:00"
  },
  "title": {
    "source": "cve",
    "received_at": "2026-10-30T12:57:41.964384+00:00"
  },
  "scores": [],
  "status": {
    "source": "cve",
    "received_at": "2026-10-30T12:57:41.964384+00:00"
  },
  "affected": [
    "cve"
  ],
  "published": {
    "source": "cve",
    "received_at": "2026-10-30T12:57:41.964384+00:00"
  },
  "solutions": [],
  "percentile": {
    "source": "epss",
    "received_at": "2026-11-03T21:16:07.982913+00:00"
  },
  "references": [
    "cve",
    "ghsa",
    "nvd"
  ],
  "description": {
    "source": "cve",
    "received_at": "2026-10-30T12:57:41.964384+00:00"
  },
  "workarounds": [],
  "configurations": []
}

Хронология записи

1. Данные обновлены04.11.2026, 00:16
2. Данные обновлены03.11.2026, 00:15
3. Данные обновлены02.11.2026, 00:13
4. Данные обновлены31.10.2026, 12:00
5. Данные обновлены30.10.2026, 20:51
6. Данные обновлены30.10.2026, 15:58
7. Данные обновлены29.10.2026, 12:47
8. Опубликована28.10.2026, 23:53

Личная заметка и статус

Другие CVE того же продукта