目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1336

100%

CVE-2026-68420— xfrm 拒绝出站策略中的可选 IPTFS 模板

AI 预测 7.8 利用难度: 中等

影响版本矩阵 8

厂商产品版本范围状态
LinuxLinuxd1716d5a44c37e5743bf6ea4e5cdbdab37727f27< d7fc6f351c478586980a521d63b0214d9c055e78affected
d1716d5a44c37e5743bf6ea4e5cdbdab37727f27< 9333f4b6f44858fc98eb12bf26b8d2959eb975d5affected
d1716d5a44c37e5743bf6ea4e5cdbdab37727f27< ea528f18231ec0f33317be57f8866913b19aba6eaffected
6.14affected
< 6.14unaffected
6.18.42≤ 6.18.*unaffected
7.1.6≤ 7.1.*unaffected
7.2-rc4≤ *unaffected
获取后续新漏洞提醒登录后订阅

一、 漏洞 CVE-2026-68420 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
xfrm: reject optional IPTFS templates in outbound policies
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: xfrm: reject optional IPTFS templates in outbound policies syzbot reported a stack-out-of-bounds read in xfrm_state_find() which flows from xfrm_tmpl_resolve_one(). Commit 3d776e31c841 ("xfrm: Reject optional tunnel/BEET mode templates in outbound policies") disallowed optional tunnel and BEET in outbound policies to prevent this. Later when IPTFS added, it was not covered by that fix and can still trigger the out-of-bounds read; Extend the check to disallow optional IPTFS in outbound policies as well. IPTFS should be identical to tunnel mode. IN and FWD policies are not affected: xfrm_tmpl_resolve_one() is only reachable via the outbound path. Reproducer, before: ip link add dummy0 type dummy ip link set dummy0 up ip addr add 10.1.1.1/24 dev dummy0 ip xfrm policy add src 10.1.1.1/32 dst 10.1.1.2/32 dir out tmpl src fc00::dead:1 dst fc00::dead:2 proto esp reqid 1 mode iptfs level use tmpl src fc00::dead:1 dst fc00::dead:2 proto esp reqid 2 mode transport ping -W 1 -c 1 10.1.1.2 PING 10.1.1.2 (10.1.1.2) 56(84) bytes of data. [ 64.168420] ================================================================== [ 64.169977] BUG: KASAN: stack-out-of-bounds in __xfrm6_addr_hash+0x11e/0x170 [ 64.169977] Read of size 4 at addr ffff88800e1ffd20 by task ping/2844 [ 64.169977] CPU: 2 UID: 0 PID: 2844 Comm: ping Not tainted 7.1.0-rc7-00180-geb23b588430a #98 PREEMPT(full) [ 64.169977] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 64.169977] Call Trace: [ 64.169977] <TASK> [ 64.169977] dump_stack_lvl+0x47/0x70 [ 64.169977] ? __xfrm6_addr_hash+0x11e/0x170 [ 64.169977] print_report+0x152/0x4b0 [ 64.169977] ? ksys_mmap_pgoff+0x6d/0xa0 [ 64.169977] ? entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 64.169977] ? rcu_read_unlock_sched+0xa/0x20 [ 64.169977] ? __virt_addr_valid+0x21b/0x230 [ 64.169977] ? __xfrm6_addr_hash+0x11e/0x170 [ 64.169977] kasan_report+0xa8/0xd0 [ 64.169977] ? __xfrm6_addr_hash+0x11e/0x170 [ 64.169977] __xfrm6_addr_hash+0x11e/0x170 [ 64.169977] __xfrm_dst_hash+0x24/0xc0 [ 64.169977] xfrm_state_find+0xa2d/0x2f90 [ 64.169977] ? __pfx_xfrm_state_find+0x10/0x10 [ 64.169977] ? __pfx_ftrace_graph_ret_addr+0x10/0x10 [ 64.169977] ? __pfx_ftrace_graph_ret_addr+0x10/0x10 [ 64.169977] xfrm_tmpl_resolve_one+0x210/0x570 [ 64.169977] ? __pfx_xfrm_tmpl_resolve_one+0x10/0x10 [ 64.169977] ? __pfx_stack_trace_consume_entry+0x10/0x10 [ 64.169977] ? kernel_text_address+0x5b/0x80 [ 64.169977] ? __kernel_text_address+0xe/0x30 [ 64.169977] ? unwind_get_return_address+0x5e/0x90 [ 64.169977] ? arch_stack_walk+0x8c/0xe0 [ 64.169977] xfrm_tmpl_resolve+0x130/0x200 [ 64.169977] ? __pfx_xfrm_tmpl_resolve+0x10/0x10 [ 64.169977] ? __pfx_xfrm_policy_inexact_lookup_rcu+0x10/0x10 [ 64.169977] ? __refcount_add_not_zero.constprop.0+0xb2/0x110 [ 64.169977] ? __pfx___refcount_add_not_zero.constprop.0+0x10/0x10 [ 64.169977] xfrm_resolve_and_create_bundle+0xd5/0x310 [ 64.169977] ? __pfx_xfrm_resolve_and_create_bundle+0x10/0x10 [ 64.169977] ? __pfx_xfrm_policy_lookup_bytype+0x10/0x10 [ 64.169977] ? __pfx_xfrm_policy_lookup_bytype+0x10/0x10 [ 64.169977] xfrm_lookup_with_ifid+0x3d8/0xb80 [ 64.169977] ? __pfx_xfrm_lookup_with_ifid+0x10/0x10 [ 64.169977] ? ip_route_output_key_hash+0xc6/0x110 [ 64.169977] ? kasan_save_track+0x10/0x30 [ 64.169977] xfrm_lookup_route+0x18/0xe0 [ 64.169977] ip4_datagram_release_cb+0x4c9/0x530 [ 64.169977] ? __pfx_ip4_datagram_release_cb+0x10/0x10 [ 64.169977] ? do_raw_spin_lock+0x71/0xc0 [ 64.169977] ? __pfx_do_raw_spin_lock+0x10/0x10 [ 64.169977] release_sock+0xb0/0x170 [ 64.169977] udp_connect+0x43/0x50 [ 64.169977] __sys_connect+0xa6/0x100 [ 64.169977] ? alloc_fd+0x2e9/0x300 [ 64.169977] ? __pfx___sys_connect+0x10/0x10 [ 64.169977] ? preempt_latency ---truncated---
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5

受影响产品

厂商产品影响版本CPE订阅
LinuxLinux d1716d5a44c37e5743bf6ea4e5cdbdab37727f27 ~ d7fc6f351c478586980a521d63b0214d9c055e78 -
LinuxLinux 6.14 -

二、漏洞 CVE-2026-68420 的公开POC

#POC 描述源链接神龙链接
AI 生成 POC高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-68420 的情报信息

登录查看更多情报信息。

CVE-2026-68420 补丁与修复 (3)

同批安全公告 · Linux · 2026-08-10 · 共 345 条

CVE-2026-68310mt76: mt7915驱动HE能力查询保护
CVE-2026-68320Linux内核SCTP协议栈认证列表容量检查漏洞
CVE-2026-68319pds_core 重置与移除死锁漏洞
CVE-2026-68318pds_core 工作队列移除时存在释放后使用漏洞
CVE-2026-68317pds_core 辅助设备添加/删除竞态漏洞
CVE-2026-68316加速驱动 Ethos-U 命令流校验元素大小处理漏洞
CVE-2026-68315SCTP协议栈在sctp_process_strreset_inreq()中验证流数
CVE-2026-68314Linux内核mctp i3c驱动注册失败处理漏洞
CVE-2026-68313TIPC __tipc_nl_compat_dumpit无限循环漏洞
CVE-2026-68312CIFS:kmalloc失败时cifsFileInfo泄漏
CVE-2026-68311mt7925无线网卡解封装卸载时STA链路保护缺陷
CVE-2026-68305drm/xe/vf CCS读写缓冲区分离时添加设备守卫
CVE-2026-68300Linux SCTP 认证模块空指针检查漏洞
CVE-2026-68301HSR 从节点注销内存泄漏漏洞
CVE-2026-68302amt: 拉取后重新读取skb头指针
CVE-2026-68303Linux内核 DRM VC4 HVS/V3D 解除绑定空指针解引用漏洞
CVE-2026-68304brcmfmac Wi-Fi驱动 802.1X-SHA256调用跟踪警告漏洞
CVE-2026-68307mt7925 WiFi驱动重置链路重播崩溃漏洞
CVE-2026-68309mt76驱动BSS HE TLV处理空指针解引用漏洞
CVE-2026-68308mt76_connac_get_he_phy_cap()返回值未检查

显示前 20 条,共 345 条。 查看全部 &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-68420

暂无评论


发表评论