CVE-2026-99133

net/iucv: fix the recvmsg window update

Published Oct 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

net/iucv: fix the recvmsg window update

iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without
testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes
the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2
is zero and one recvmsg() on its own socket is enough for an unprivileged
process to take a spurious disconnect.

It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which
allocates GFP_KERNEL inside a section the code treats as atomic. Sending
outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where
msg_recv is sampled for the advertised window and subtracted after
dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock()
while recvmsg holds no socket lock, so both can subtract the same value,
the counter goes negative and the credit reaches the peer twice.

Test the transport, claim the credit with atomic_xchg() after the last
error exit and hand it back if the transmit fails, and send once the lock
is dropped.

Analysis

AI-generated

Technical impact

The fix addresses an issue in the Linux kernel’s IUCV socket implementation where the recvmsg() function would send a window update flag without verifying the transport type. On classic z/VM sockets this results in a NULL pointer dereference for the HiperSockets device, causing a spurious disconnect for an unprivileged process. Additionally, the code incorrectly allocates memory while holding a spin lock that is treated as atomic, allowing concurrent recvmsg() calls to manipulate a shared credit counter. This can lead to the counter becoming negative and the peer receiving credit twice, potentially allowing an attacker to affect the flow control state. The vulnerability is mitigated by the patch; before the fix, an attacker could exploit it to induce denial‑of‑service or disrupt kernel IUCV communication.

Affected Systems

The vulnerability impacts Linux kernel implementations that provide the IUCV socket interface, specifically those versions that include the buggy recvmsg() logic. No specific kernel releases are listed in the data; the issue applies to any kernel that has not yet applied the kernel commit that introduces the fix. The affected systems are all machines running a Linux kernel that supports IUCV sockets.

Risk and Exploitability

The CVSS score is 5.5, EPSS is < 1%, and it is not listed in KEV, indicating a moderate risk level. Because the flaw is triggered by unprivileged processes calling recvmsg() on a classic z/VM socket, an attacker could readily trigger the fault without special access. The potential impact includes causing unnecessary socket disconnects and out‑of‑range credit counters, which could degrade system reliability or create a subtle denial‑of‑service vector. The EPSS score of < 1% indicates a low exploitation probability, and the absence in KEV suggests no widespread, active exploits have been reported yet.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that has incorporated the commit fixing iucv_sock_recvmsg() and related atomic allocation issues
  • Verify that the kernel's IUCV socket implementation is compiled with the necessary configuration to prevent window updates on non‑HiperSockets transports
  • If an immediate kernel upgrade is not feasible, monitor for kernel updates from trusted provenance and apply them as soon as possible
  • Ensure that only trusted and necessary processes can call recvmsg() on IUCV sockets by employing proper capability or user namespace restrictions

Generated by OpenCVE AI on October 30, 2026 at 02:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
History
Type Values Removed Values Added
Weaknesses CWE-476
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-665
CWE-682
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix the recvmsg window update iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect. It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice. Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.
Title net/iucv: fix the recvmsg window update
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:42 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 30, 2026, 1:21 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:34 AM