CVE-2026-81003
net/iucv: filter frames in afiucv_hs_rcv() by ingress device
Reported by linux · Published September 11, 2026
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.
EPSS 0.31% · 24.2th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-core | errata.rockylinux.org | 5.14.0-687.58.1.el9 |
| kernel-abi-stablelists | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.el8, 0:4.18.0-553.178.1.el8_10.noarch |
| perf | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.el8, 0:4.18.0-553.178.1.el8_10.x86_64, 0:4.18.0-553.178.1.el8_10.aarch64 |
| kernel-modules-core | errata.rockylinux.org | 5.14.0-687.58.1.el9 |
| libperf-debuginfo | errata.rockylinux.org | 5.14.0-687.58.1.el9 |
| kernel-modules-extra | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.el8, 0:4.18.0-553.178.1.el8_10.x86_64, 0:4.18.0-553.178.1.el8_10.aarch64 |
| libperf | errata.rockylinux.org | 5.14.0-687.58.1.el9 |
| kernel-debug-core | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.el8, 0:4.18.0-553.178.1.el8_10.x86_64 |
| kernel-tools | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.el8, 0:4.18.0-553.178.1.el8_10.x86_64, 0:4.18.0-553.178.1.el8_10.aarch64 |
| kernel-64k-debug-modules-extra | errata.rockylinux.org | 5.14.0-687.58.1.el9 |
| kernel-rt-debug | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.rt7.519.el8, 0:4.18.0-553.178.1.rt7.519.el8_10.x86_64 |
| kernel-rt-debug-devel | errata.rockylinux.org | 5.14.0-687.58.1.el9, 4.18.0-553.178.1.rt7.519.el8, 0:4.18.0-553.178.1.rt7.519.el8_10.x86_64 |
44 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3881ac441f642d56503818123446f7298442236b, 3881ac441f642d56503818123446f7298442236b, 3881ac441f642d56503818123446f7298442236b |
| Linux | Linux | 3.2, 0, 5.10.270 |
| linux | linux_kernel | 3.2, 3.2, 3.2 |
| Linux | Linux | 3881ac441f642d56503818123446f7298442236b, 3881ac441f642d56503818123446f7298442236b, 3881ac441f642d56503818123446f7298442236b |
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (25 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Oct 19, 2026 CVE Updated
- Oct 22, 2026 Distribution Patch (4 in total, the first dated here)
- Oct 30, 2026 Security Advisory (2 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-81003
vulnetix vdb fixes CVE-2026-81003
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-81003/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart