cve.bz

CVE-2026-81003 linux linux

8.1 highEPSS 0.3%Fix available

High (8.1) in linux linux. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.270
  • Linux Linux: fixed in 5.15.221
  • Linux Linux: fixed in 6.1.188
  • Linux Linux: fixed in 6.6.157
  • Linux Linux: fixed in 6.12.109
  • Linux Linux: fixed in 6.18.50
  • Linux Linux: fixed in 7.2.4
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Red Hat, openSUSE, AlmaLinux, Rocky Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-81003 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-81003?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-81003?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-81003 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.270
Linux5.155.15.221
Linux6.16.1.188
Linux6.66.6.157
Linux6.126.12.109
Linux6.186.18.50
Linux7.27.2.4
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-81003
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-81003
Debian13linux6.12.111-1DEBIAN-CVE-2026-81003
Debian14linux7.2.6-1DEBIAN-CVE-2026-81003
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-81003
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-81003
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-81003
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-81003 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-81003 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-81003 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-81003 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-81003 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-81003 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-81003 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-81003 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-81003 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-553.178.1.el8_10RHSA-2026:89083
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-553.178.1.el8_10RHSA-2026:89083
Red Hatenterprise_linux:8::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 12 more0:4.18.0-553.178.1.rt7.519.el8_10RHSA-2026:89082
Red Hatenterprise_linux:8::realtimekernel-rt, kernel-rt-core, kernel-rt-debug and 10 more0:4.18.0-553.178.1.rt7.519.el8_10RHSA-2026:89082
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.58.1.el9_8RHSA-2026:83156
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.58.1.el9_8RHSA-2026:83156
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.58.1.el9_8RHSA-2026:83156
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.58.1.el9_8RHSA-2026:83156
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.58.1.el9_8RHSA-2026:83156
Red Hatenterprise_linux:10.3rv, perf, rtla and 89 more0:6.12.0-264.14.1.el10_3RHSA-2026:98608
openSUSETumbleweedkernel-source7.2.6-1.1openSUSE-SU-2026:11805-1
AlmaLinux8kernel-rt, kernel-rt-core, kernel-rt-debug and 7 more4.18.0-553.178.1.rt7.519.el8_10ALSA-2026:89082
AlmaLinux8perf, kernel, bpftool and 22 more4.18.0-553.178.1.el8_10ALSA-2026:89083
AlmaLinux9rv, perf, rtla and 71 more5.14.0-687.58.1.el9_8ALSA-2026:83156
Rocky Linux8kernel0:4.18.0-553.178.1.el8_10RLSA-2026:89083
Rocky Linux8kernel-rt0:4.18.0-553.178.1.rt7.519.el8_10RLSA-2026:89082
Rocky Linux9kernel0:5.14.0-687.58.1.el9_8RLSA-2026:83156
Azure Linux3kernelno fix listedAZL-100073
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-81003
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-81003
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-81003

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw rated IMPORTANT by Red Hat Product Security was found in the Linux kernel's AF_IUCV protocol implementation, used for the z/VM IUCV and HiperSockets transports on the s390x (IBM Z) architecture. The afiucv_hs_rcv() receive path selected a target socket from the global socket list by matching only the four 8-byte name fields in the frame's transport header, without checking the network device the frame arrived on. As a result, a frame received on any network device could be delivered to an AF_IUCV socket bound to a different device or to the classic z/VM IUCV transport. A local attacker holding only the CAP_NET_RAW capability inside an unprivileged user and network namespace could send a raw ETH_P_AF_IUCV frame on its own loopback device and have it matched against sockets in the initial network namespace; similarly, a host on the same shared HiperSockets segment could direct frames at sockets bound to a different HiperSockets device. Successful exploitation could exhaust a listening socket's accept queue (denial of service), inject data into existing AF_IUCV connections, control the peer identity of accepted child sockets, and disrupt or kill established connections. Multiple Red Hat Enterprise Linux kernel and kernel-rt update streams and Red Hat In-Vehicle OS kernel streams are affected, and fixes are being pursued in the respective product streams; the kernel-ivos-qualcomm component of Red Hat In-Vehicle OS is not affected because the vulnerable code is not present in that kernel. The Red Hat severity of IMPORTANT (CVSS 3.1 score 7.0, AV:L/AC:H/PR:L) is lower than the upstream CVE.org rating of 8.1 (AV:A/AC:L/PR:N): Red Hat assessed the dominant exploitation path as local, requiring privileges and high attack complexity, whereas the upstream rating emphasizes the adjacent-network HiperSockets vector requiring no privileges. Note that AF_IUCV over HiperSockets provides no per-connection authentication, so the fix reduces the attack surface to peers present on the same HiperSockets segment but does not change that protocol-level property.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-264.14.1.el10_3Fixed 2026-11-11RHSA-2026:98608
Red Hat Enterprise Linux 8kernel-rt-0:4.18.0-553.178.1.rt7.519.el8_10Fixed 2026-10-24RHSA-2026:89082
Red Hat Enterprise Linux 8kernel-0:4.18.0-553.178.1.el8_10Fixed 2026-10-24RHSA-2026:89083
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.58.1.el9_8Fixed 2026-10-14RHSA-2026:83156
Red Hat OpenShift Container Platform 4.22openshift/ose-rhel-coreos-9:4.22.9.8.202610241758-0Fixed 2026-10-27RHSA-2026:89197
Red Hat Enterprise Linux 6kernelUnder investigation
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-81003.

References

Check your stackJSON