CVE-2026-81003— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于afiucv_hs_rcv()未验证帧的入口设备，可能导致帧被传递到不匹配的套接字，造成拒绝服务、数据注入或连接终止。
可能的 ATT&CK 技术 2 AI
T1190 · Exploit Public-Facing Application T1210 · Exploitation of Remote Services影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 3881ac441f642d56503818123446f7298442236b< 639828ad4d374056167391dbaffd13dd5e5e5ddb |
affected |
3881ac441f642d56503818123446f7298442236b< 92e5c281f1caa287bb58292f2687c9e3ff3aa23e |
affected | ||
3881ac441f642d56503818123446f7298442236b< 712330f8a4293cfd97b0d62b7c7dc01862a16b98 |
affected | ||
3881ac441f642d56503818123446f7298442236b< 0a5af67e7184c6a0e155c317840bd64b37177af4 |
affected | ||
3881ac441f642d56503818123446f7298442236b< dfac2936b83be00035ae176f8252e1c1e1de9207 |
affected | ||
3881ac441f642d56503818123446f7298442236b< 8e3763f1ccac3fc395f9af2b87114c023ced8a3f |
affected | ||
3881ac441f642d56503818123446f7298442236b< a7f0130a091724e69827ab58e74777a88747e892 |
affected | ||
3881ac441f642d56503818123446f7298442236b< 80230a18c164a4b5bbc048fe2768b219ac17bc5a |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-81003 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net/iucv: filter frames in afiucv_hs_rcv() by ingress device
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net/iucv: filter frames in afiucv_hs_rcv() by ingress device
afiucv_hs_rcv() selects a socket from iucv_sk_list by matching four 8-byte
name fields in the transport header alone. No check is made against the
net_device the frame arrived on.
This can cause a frame arriving on any netdev to be delivered to an AF_IUCV
socket. Three problems follow.
First, a frame arriving over HiperSockets can be delivered to a socket
bound to the classic z/VM IUCV transport, which has iucv->hs_dev == NULL.
iucv_sock_bind() takes the classic path whenever the requested userid
matches iucv_userid, even on a guest that also has a HiperSockets device
carrying the same identifier. The child socket created by
afiucv_hs_callback_syn() for such a match inherits hs_dev = NULL and
transport = AF_IUCV_TRANS_HIPER, so the first send() on it returns -ENODEV.
The socket delivered to accept() is unusable.
Second, a frame arriving on one netdev can be delivered to a socket bound
to a different IQD device. Which can lead to
- Accept-queue exhaustion (DoS)
- Attacker-controlled peer identity in the child socket
- Data injection into existing sockets
- Fabric noise on the IQD fabric, where bogus replies are sent
- killing established connections
Third, all AF_IUCV sockets live in init_net, as iucv_sock_alloc() calls
sk_alloc(&init_net, ...). But even frames arriving on netdev devices in a
namespace can be delivered to an IUCV socket. So a process in an
unprivileged user and network namespace holding only the CAP_NET_RAW
capability valid within that namespace can send a raw ETH_P_AF_IUCV frame
on its own lo device and have it matched against init_net sockets.
Fix all three by skipping any socket whose hs_dev does not match the
ingress device. A classic z/VM IUCV socket has hs_dev == NULL; the ingress
dev is never NULL, so classic sockets are skipped automatically. An unbound
HIPER socket also has hs_dev == NULL and is skipped. A bound HIPER socket
is only reachable from the exact IQD device it was bound to. Because hs_dev
is always a device in init_net (iucv_sock_bind() scans
for_each_netdev_rcu(&init_net, ...) exclusively), a frame whose ingress
device belongs to another namespace never matches any socket.
Note that AF_IUCV over HiperSockets provides no per-connection
authentication: no sequence numbers, no TLS, no nonce. The four name fields
identifying a connection are exchanged in plaintext on the shared
HiperSockets segment (VCHID). Any host on the same HiperSockets segment
could spoof any frame type against an existing connection. That is a
protocol-level property unchanged by this patch. The fix reduces the attack
surface to peers present on the same HiperSockets segment.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于afiucv_hs_rcv()未验证帧的入口设备，可能导致帧被传递到不匹配的套接字，造成拒绝服务、数据注入或连接终止。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-81003 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-81003 的情报信息
请登录查看更多情报信息。
CVE-2026-81003 补丁与修复 (7)
同批安全公告 · Linux · 2026-09-11 · 共 431 条
| CVE-2026-89688 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89656 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89655 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89658 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89660 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89659 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89662 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89669 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89674 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89675 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89676 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89677 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89681 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89686 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89478 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89479 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89702 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89703 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89482 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-89708 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
显示前 20 条，共 431 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-81003
暂无评论