CVE-2026-99033— Linux 内核 net/packet 远程代码执行漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已得到修复： net/packet: 在 packet_rcv_spkt() 中对链路层头部推送操作增加保护 函数通过以下代码恢复链路层头部： 然而，该减法运算仅在设备实际拥有链路层头部时才有意义。 和 均通过 对该操作进行了封装保护，且文件顶部的块注释也明确指出恢复操作应基于该谓词；但 却未包含此保护。 提交 d549699048b4（"net/packet: 修复在无可见硬头部的 L3 设备上接收数据包的问题"）引入了该辅助函数并修改了两个调用点，但遗漏了 这一处。 对于没有可见
可能的 ATT&CK 技术 1 AI
T1499.003 · Application Exhaustion Flood影响版本矩阵 14
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | d549699048b4b5c22dd710455bcdb76966e55aa3< d8a24b9e1774a93943caf68d48c5e17be432220b |
affected |
d549699048b4b5c22dd710455bcdb76966e55aa3< 31c7b15b3716e8d0dad58d2c3cdf321dfd06f4be |
affected | ||
d549699048b4b5c22dd710455bcdb76966e55aa3< 3efe0e0944157fdd2072b4dc7eb0491a317ed272 |
affected | ||
d549699048b4b5c22dd710455bcdb76966e55aa3< 00fbf71e74115f7628fc0880b855434b1e70c40c |
affected | ||
d549699048b4b5c22dd710455bcdb76966e55aa3< 28bc1ef699610ee09ce3d46a00552f5a0a0144bd |
affected | ||
dadddde259a19105ee69e788835f4d4552767aa9 |
affected | ||
5.9.13< 5.10 |
affected | ||
5.10 |
affected | ||
| … +6 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-99033 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net/packet: guard the ll header push in packet_rcv_spkt()
来源: CVE Program / CVE List V5
Vulnerability 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.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-99033 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-99033 的情报信息
请登录查看更多情报信息。
CVE-2026-99033 补丁与修复 (5)
同批安全公告 · Linux · 2026-10-23 · 共 217 条
| CVE-2026-98959 | 9.8 CRITICAL | btrfs 扩展属性替换处理远程代码执行漏洞 |
| CVE-2026-99078 | 9.8 CRITICAL | Mellanox mlx5e MPWQE重试时XSK缓冲区释放漏洞 |
| CVE-2026-99079 | 9.8 CRITICAL | Mellanox mlx5e 驱动 XSK 缓冲区释放漏洞 |
| CVE-2026-98988 | 8.8 HIGH | Linux 5.13 命名空间越界漏洞 |
| CVE-2026-99083 | 8.8 HIGH | ksmbd 的 krb5_authenticate() 函数堆越界写漏洞 |
| CVE-2026-99082 | 8.8 HIGH | KVM x86 内存管理漏洞 |
| CVE-2026-98981 | 8.8 HIGH | Linux 内核命名空间 dentry 解挂载前未哈希漏洞 |
| CVE-2026-98980 | 8.8 HIGH | namei 遍历中过度挂载条目信息泄露漏洞 |
| CVE-2026-98870 | 8.8 HIGH | ksmbd 会话清理时存在通道移除逻辑漏洞 |
| CVE-2026-98978 | 8.4 HIGH | Linux 命名空间 锁定挂载永不失效漏洞 |
| CVE-2026-99042 | 8.4 HIGH | io_uring 24 字节 sockaddr_in6 过滤字段填充漏洞 |
| CVE-2026-98968 | 8.1 HIGH | AMT 中继通用查询远程代码执行漏洞 |
| CVE-2026-99064 | 8.1 HIGH | CIPSO 缓存选项偏移调整漏洞 |
| CVE-2026-99014 | 7.8 HIGH | Linux 蓝牙 hci_sync 命令 skb 生命周期漏洞 |
| CVE-2026-98999 | 7.8 HIGH | Intel Xe DRM 驱动程序链接表项失效漏洞 |
| CVE-2026-99016 | 7.8 HIGH | RISC-V futex 用户指针未去标签原子访问漏洞 |
| CVE-2026-99018 | 7.8 HIGH | RISC-V 内核影子调用栈加载逻辑缺陷 |
| CVE-2026-99051 | 7.8 HIGH | fsverity 信息结构释放延迟漏洞 |
| CVE-2026-99054 | 7.8 HIGH | Linux TIPC 拓扑服务队列资源泄漏漏洞 |
| CVE-2026-99053 | 7.8 HIGH | Linux TIPC 节点引用漏洞 |
显示前 20 条，共 217 条。 查看全部 → →