CVE-2026-98401— IP隧道解封装时传输头部 stale 问题
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
以下是该漏洞描述信息的中文翻译： 在 Linux 内核中，已解决以下漏洞： 网络：iptunnel：修复隧道解封装期间传输头（transport header）过时的问题 Syzbot 报告称，在 中发生崩溃，其原因是在隧道解封装后， 偏移量过时（stale）。 该问题在 commit （"net: pull headers in qdisc_pkt_len_segs_init()"）引入 qdisc 读取传输头之前完全潜伏。崩溃需要以下四个条件同时满足： 1. 传入的数据包是封装的并携带 GSO（通用分段卸载）元
可能的 ATT&CK 技术 1 AI
T1190 · Exploit Public-Facing Application影响版本矩阵 10
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 8c3d4dfcecf7670c1d752f1ae74b21b2af5feac1 |
affected |
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< e4a5b01e59f7102169762b8f566c8e052d05c0ff |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 3340b8565b85631cfeb0df049e8b46e3ef8bd7bd |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 28a57fb2c5df4deb42a06e52fd36c14b37aa0034 |
affected | ||
2.6.12 |
affected | ||
< 2.6.12 |
unaffected | ||
6.12.111≤ 6.12.* |
unaffected | ||
6.18.53≤ 6.18.* |
unaffected | ||
| … +2 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-98401 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net: iptunnel: fix stale transport header during tunnel decapsulation
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net: iptunnel: fix stale transport header during tunnel decapsulation
Syzbot reported a crash in qdisc_pkt_len_segs_init() caused by a stale
transport_header offset after tunnel decapsulation.
BUG: unable to handle page fault for address: ffffed102091a42e
Oops: Oops: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 340 Comm: qdisc_uaf_repro Not tainted 7.2.0-rc4-00061-g248951ddc14d #256 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__asan_load2
<IRQ>
qdisc_pkt_len_segs_init (net/core/dev.c:4145)
__dev_queue_xmit (net/core/dev.c:4787)
br_dev_queue_push_xmit (net/bridge/br_forward.c:53)
br_handle_frame_finish (net/bridge/br_input.c:229)
br_handle_frame (net/bridge/br_input.c:315)
__netif_receive_skb_core.constprop.0 (net/core/dev.c:6099)
__netif_receive_skb_list_core (net/core/dev.c:6287)
netif_receive_skb_list_internal (net/core/dev.c:6445)
napi_complete_done (net/core/dev.c:6813)
gro_cell_poll (net/core/gro_cells.c:74)
__napi_poll (net/core/dev.c:7735)
net_rx_action (net/core/dev.c:7798 net/core/dev.c:7955)
handle_softirqs (kernel/softirq.c:622)
do_softirq (kernel/softirq.c:523 kernel/softirq.c:510 )
__local_bh_enable_ip (kernel/softirq.c:450)
tun_get_user (drivers/net/tun.c:1986 (discriminator 1))
tun_chr_write_iter (drivers/net/tun.c:2032)
The issue is completely latent until qdisc read transport header in
commit 7fb4c1967011 ("net: pull headers in qdisc_pkt_len_segs_init()").
The crash requires four conditions to line up:
1. The incoming packet is encapsulated and carries GSO metadata. The outer
transport header offset is stored in skb->transport_header while the
packet is still in the outer tunnel context.
2. The tunnel receiver strips the outer headers. skb->data is advanced to
the inner frame, but skb->transport_header is left pointing to the
now-removed outer L4 header, so it becomes a negative offset relative to
the new data.
3. The inner frame is not delivered to the local IP stack. Instead, it
is forwarded at L2 by a bridge or HSR, so ip_rcv_core() never runs and
the transport header is not reset to the inner L4 offset.
4. The forwarding path calls __dev_queue_xmit(), which enters
qdisc_pkt_len_segs_init(). That function computes the GSO header length
from skb_transport_offset(skb). Because the offset is negative, the
unsigned cast overflows and pskb_may_pull(skb, hdr_len +
sizeof(struct tcphdr)) reads past the end of the skb, triggering a
KASAN fault or page fault.
The issue specifically requires GSO packets (shinfo->gso_size != 0), which
are processed/aggregated through gro_cells. Fix this by clearing
transport_header to the ~0U sentinel in gro_cell for all tunnnel driver.
GTP does not support GRO/GSO, drop the evil GSO packets in GTP directly.
来源: 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-98401 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-98401 的情报信息
请登录查看更多情报信息。
CVE-2026-98401 其他参考 (4)
同批安全公告 · Linux · 2026-10-14 · 共 46 条
| CVE-2026-98398 | 锁依赖（lockdep）清空类缓存条目漏洞 | |
| CVE-2026-98396 | PowerPC KUAP恢复漏洞 | |
| CVE-2026-98393 | IPv4 UDP长度溢出漏洞 | |
| CVE-2026-98391 | drm/xe: 运行时PM检查缺失导致页面故障工作器漏洞 | |
| CVE-2026-98389 | AMD GPU驱动重置时跳过显卡切换电源配置文件漏洞 | |
| CVE-2026-98388 | exec: 在获取 exec_update_lock 前调用 do_close_on_exec() | |
| CVE-2026-98387 | s390/crypto: 修复aes_s390中skcipher_walk返回值处理漏洞 | |
| CVE-2026-98386 | qla2xxx 使用 memset_io() 清理 QLAFX00 请求环槽 | |
| CVE-2026-98390 | AMD节点：虚拟化系统除零漏洞 | |
| CVE-2026-98397 | x86-android-tablets 二次fwnode销毁时持设备引用漏洞 | |
| CVE-2026-98395 | PowerPC IRQ软掩码损坏漏洞 | |
| CVE-2026-98399 | s390/ipl：修复dump_reipl中缺少re-IPL参数块时的空指针解引用漏洞 | |
| CVE-2026-98400 | Linux内核s390 ipl空指针解引用漏洞 | |
| CVE-2026-98402 | net: icmp: 避免在 icmp_send 跟踪点中访问无效传输头 | |
| CVE-2026-98403 | s390系统初始化参数溢出漏洞 | |
| CVE-2026-98404 | virtio GPU 用户帧缓冲区创建空指针错误 | |
| CVE-2026-98405 | smb 客户端 parse_posix_sids 函数缺失边界检查漏洞 | |
| CVE-2026-98406 | mac80211 驱动程序中避免警告的位速率掩码漏洞 | |
| CVE-2026-98408 | rzv2h 看门狗除零漏洞 | |
| CVE-2026-98407 | RSI 无线驱动 密钥移除时堆越界写入漏洞 |
显示前 20 条，共 46 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-98401
暂无评论