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

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2026-98595— Linux 内核 UDP 4 元组哈希表移除漏洞

一分钟漏洞结论

影响对象
Linux Linux
利用判断
尚无明确在野利用证据,仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本;无法立即升级时,限制受影响服务暴露并加强监测。

在 Linux 内核中,以下漏洞已得到修复: UDP:从四元组哈希表中移除已断开的套接字 当一个 UDP 套接字绑定到特定地址和端口后,即使该套接字已断开连接,其条目仍会保留在四元组哈希表中: 函数仅在调用 或 时作为副作用将套接字从该表中移除;当设置 时会跳过 ,当设置 时会跳过 。此前提交 ("udp: Unhash auto-bound connected sk from 4-tuple hash table when disconnected.")通过另一条执行路径修复了通配符绑定套接字在断开后出现相同最终

AI 预测 6.5 利用难度: 中等
获取后续新漏洞提醒 登录后订阅

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

漏洞信息

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

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

Vulnerability Title
udp: remove a disconnected socket from the 4-tuple hash table
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: udp: remove a disconnected socket from the 4-tuple hash table A UDP socket bound to a specific address and port keeps its entry in the 4-tuple hash table after it is disconnected: sk binds to 127.0.0.1:21001 sk connects to 127.0.0.2:20001 // filed in the 4-tuple table sk disconnects, connect(AF_UNSPEC) // still filed, peer now 0.0.0.0:0 __udp_disconnect() takes a socket out of that table only as a side effect of ->rehash() or ->unhash(), and it skips ->rehash() when SOCK_BINDADDR_LOCK is set and ->unhash() when SOCK_BINDPORT_LOCK is set. commit 6996a2d2d0a6 ("udp: Unhash auto-bound connected sk from 4-tuple hash table when disconnected.") fixed the same end state for a wildcard-bound socket, by a path this one does not take. The entry is counted whether or not anything hits it. hash4_cnt on the hash2 slot stays raised for as long as the socket lives, so udp_has_hash4() keeps sending every packet for that address and port through the 4-tuple lookup first. On IPv6 it can also be hit. __udp_disconnect() does not clear sk_v6_daddr, so udp_v6_rehash() files the entry under the peer the socket was connected to with a zero dport, and inet6_match() compares that same field: a datagram from the former peer with a zero source port matches, and source port zero is accepted on receive. On IPv4 the peer is cleared, so a match would need a zero source address as well, which the routing layer rejects as martian. The stale sk_v6_daddr is a separate defect, not addressed here; removing the entry closes this path either way. The entry can also be relocated. __udp_disconnect() clears sk_bound_dev_if, so a subsequent SO_BINDTODEVICE calls ->rehash(), and because the receive address is still specific udp_lib_rehash() moves the entry instead of removing it, into the bucket that (rcv_saddr, num, 0, 0) hashes to -- a pure function of the address and port, so every socket reaching this state on one address and port collects in one bucket. The bucket cannot be chosen from outside, as udp_ehashfn() is seeded with a per-boot secret. This last one became reachable only with commit 644f9108f3a5 ("udp: Make rehash4 independent in udp_lib_rehash()"), which moved the hash4 handling out of a branch a disconnected socket does not take; the stale entry itself dates from the commit in Fixes. Take the socket out of the table before __udp_disconnect() runs, while it still matches how it was filed. This also reaches the wildcard case ahead of udp_lib_rehash()'s udp_unhash4() branch, leaving that branch unreachable from udp_disconnect(); removing it belongs in net-next. udp_disconnect() and udp_abort() are the only UDP entries into __udp_disconnect(), which is shared with raw, ping and l2tp sockets that are not struct udp_sock: ping_prot.obj_size is sizeof(struct inet_sock), so udp_hashed4() on one would read past the allocation.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5

受影响产品

厂商 产品 影响版本 CPE 订阅
Linux Linux 78c91ae2c6deb5d236a5a93ff2995cdd05514380 ~ c21daf37d5ce9a4e234b7c42238ac1e6041e28e4 -
Linux Linux 6.13 -

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

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

未找到公开 POC。

登录以生成 AI POC

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

请登录查看更多情报信息。

CVE-2026-98595 其他参考 (3)

同批安全公告 · Linux · 2026-10-18 · 共 436 条

CVE-2026-98582 ST21NFCA NFC 驱动接收帧大小验证漏洞
CVE-2026-98568 Linux vxlan 邻居回复内存使用漏洞
CVE-2026-98570 Linux IPv6 子网路由表项处理信息泄露漏洞
CVE-2026-98571 stmmac 驱动 skb 构建失败后内存泄漏漏洞
CVE-2026-98572 bpf MIPS32 JEQ/JNE 跳转指令逻辑漏洞
CVE-2026-98573 Linux 内核 IPv6 校验和计算整数下溢漏洞
CVE-2026-98574 bcmgenet 网络驱动 NAPI 停止前禁用队列漏洞
CVE-2026-98575 pn533 NFC 驱动越界读取漏洞
CVE-2026-98576 Linux NFC LLCP 服务名日志越界读漏洞
CVE-2026-98577 NFC LLCP 模块 WKS SAP 劫持漏洞
CVE-2026-98578 Linux st21nfca ISO15693 库存长度验证漏洞
CVE-2026-98579 NFC LLCP SDreq TLV 列表泄露漏洞
CVE-2026-98580 Linux NFC LLCP 接受队列生命周期竞态条件漏洞
CVE-2026-98581 NFC LLCP nfc_llcp_recv_dm 列表损坏/引用计数不同步
CVE-2026-98593 Linux s390 调试功能空指针解引用漏洞
CVE-2026-98590 bpf 上下文代码生成逻辑修复
CVE-2026-98591 bpf skb 动态指针越界漏洞
CVE-2026-98592 Spacemit 网络驱动传输描述符处理漏洞
CVE-2026-98589 bpf 子程序拒绝 pkt 参数
CVE-2026-98594 tg3 驱动 PHYLIB 资源清理漏洞

显示前 20 条,共 436 条。 查看全部 → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-98595

暂无评论


发表评论