In the Linux kernel, the following vulnerability has been resolved: net/iucv: filter frames in afiucv_hs_rcv() by ingress device afiucv_hs_rcv()… (CVE-2026-81003)
A vulnerability in the Linux kernel's AF_IUCV socket handling over HiperSockets was resolved. The issue allowed frames arriving on any network device to be delivered to AF_IUCV sockets without verifying the ingress device, leading to multiple security problems including denial of service, identity spoofing, data injection, and cross-namespace socket access. The fix ensures that only sockets bound to the exact ingress device receive frames, preventing these issues. The underlying protocol lacks per-connection authentication, so some spoofing risks remain inherent to the protocol design.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-81003 involves the afiucv_hs_rcv() function, which selects AF_IUCV sockets based solely on transport header name fields without verifying the ingress network device. This flaw allows frames from any netdev to be delivered to sockets bound to different devices or namespaces, causing accept-queue exhaustion (DoS), attacker-controlled peer identity, data injection, fabric noise, and killing established connections. Additionally, processes in unprivileged network namespaces with CAP_NET_RAW can send frames that match sockets in the init_net namespace. The patch fixes this by skipping sockets whose bound device (hs_dev) does not match the ingress device, effectively isolating sockets to their correct network devices and namespaces. The protocol itself lacks per-connection authentication, so some spoofing risks remain but the attack surface is reduced.
Potential Impact
The vulnerability can lead to denial of service via accept-queue exhaustion, unauthorized data injection into existing sockets, attacker-controlled peer identity spoofing, disruption of IQD fabric communications, and unauthorized cross-namespace socket access. It affects the integrity and availability of AF_IUCV socket communications over HiperSockets in the Linux kernel. However, the protocol's inherent lack of per-connection authentication means some spoofing risks remain despite the fix.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to ensure afiucv_hs_rcv() filters frames by the ingress device, preventing delivery to sockets bound to different devices or namespaces. Users should apply the official kernel update that includes this patch. No additional mitigation is required as the patch addresses the vulnerability directly.
In the Linux kernel, the following vulnerability has been resolved: net/iucv: filter frames in afiucv_hs_rcv() by ingress device afiucv_hs_rcv()… (CVE-2026-81003)
Description
A vulnerability in the Linux kernel's AF_IUCV socket handling over HiperSockets was resolved. The issue allowed frames arriving on any network device to be delivered to AF_IUCV sockets without verifying the ingress device, leading to multiple security problems including denial of service, identity spoofing, data injection, and cross-namespace socket access. The fix ensures that only sockets bound to the exact ingress device receive frames, preventing these issues. The underlying protocol lacks per-connection authentication, so some spoofing risks remain inherent to the protocol design.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-81003 involves the afiucv_hs_rcv() function, which selects AF_IUCV sockets based solely on transport header name fields without verifying the ingress network device. This flaw allows frames from any netdev to be delivered to sockets bound to different devices or namespaces, causing accept-queue exhaustion (DoS), attacker-controlled peer identity, data injection, fabric noise, and killing established connections. Additionally, processes in unprivileged network namespaces with CAP_NET_RAW can send frames that match sockets in the init_net namespace. The patch fixes this by skipping sockets whose bound device (hs_dev) does not match the ingress device, effectively isolating sockets to their correct network devices and namespaces. The protocol itself lacks per-connection authentication, so some spoofing risks remain but the attack surface is reduced.
Potential Impact
The vulnerability can lead to denial of service via accept-queue exhaustion, unauthorized data injection into existing sockets, attacker-controlled peer identity spoofing, disruption of IQD fabric communications, and unauthorized cross-namespace socket access. It affects the integrity and availability of AF_IUCV socket communications over HiperSockets in the Linux kernel. However, the protocol's inherent lack of per-connection authentication means some spoofing risks remain despite the fix.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to ensure afiucv_hs_rcv() filters frames by the ingress device, preventing delivery to sockets bound to different devices or namespaces. Users should apply the official kernel update that includes this patch. No additional mitigation is required as the patch addresses the vulnerability directly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5r93-38xq-57mx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81003"]
Threat ID: 6aa4a02855bf5e2cf5a86b1b
Added to database: 09/12/2026, 00:43:20 UTC
Last enriched: 09/12/2026, 01:20:38 UTC
Last updated: 09/12/2026, 01:20:38 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.