In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix locking in .getsockopt Mirror iucv_sock_setsockopt() and wrap the… (CVE-2026-64004)
In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix locking in .getsockopt Mirror iucv_sock_setsockopt() and wrap the whole switch in lock_sock()/release_sock(). The pre-existing SO_MSGLIMIT-only lock becomes redundant and is removed. Any AF_IUCV HIPER user can potentially crash the kernel by racing recvmsg() with getsockopt(SO_MSGSIZE): the SO_MSGSIZE arm dereferences iucv->hs_dev->mtu after iucv_sock_close() (called from the racing recvmsg()) has set hs_dev to NULL, producing a NULL pointer dereference oops.
AI Analysis
Technical Summary
The Linux kernel net/iucv subsystem had a race condition vulnerability in the getsockopt handler for SO_MSGSIZE. Specifically, the code did not properly lock around the getsockopt call, allowing a race with recvmsg() and iucv_sock_close(). This race could cause a NULL pointer dereference when accessing iucv->hs_dev->mtu after hs_dev was set to NULL by iucv_sock_close(), resulting in a kernel crash (NULL pointer dereference oops). The fix involved mirroring the locking strategy used in iucv_sock_setsockopt() by wrapping the entire switch statement in lock_sock()/release_sock() calls and removing a now redundant SO_MSGLIMIT-only lock.
Potential Impact
An attacker with access to AF_IUCV HIPER sockets could trigger a race condition causing a kernel NULL pointer dereference and crash, resulting in a denial of service. There is no indication of privilege escalation or code execution. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code to properly lock the getsockopt handler and prevent the race condition. Users should apply the official kernel updates that include this fix. Since this is not a cloud service, remediation depends on deploying patched kernel versions. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix locking in .getsockopt Mirror iucv_sock_setsockopt() and wrap the… (CVE-2026-64004)
Description
In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix locking in .getsockopt Mirror iucv_sock_setsockopt() and wrap the whole switch in lock_sock()/release_sock(). The pre-existing SO_MSGLIMIT-only lock becomes redundant and is removed. Any AF_IUCV HIPER user can potentially crash the kernel by racing recvmsg() with getsockopt(SO_MSGSIZE): the SO_MSGSIZE arm dereferences iucv->hs_dev->mtu after iucv_sock_close() (called from the racing recvmsg()) has set hs_dev to NULL, producing a NULL pointer dereference oops.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel net/iucv subsystem had a race condition vulnerability in the getsockopt handler for SO_MSGSIZE. Specifically, the code did not properly lock around the getsockopt call, allowing a race with recvmsg() and iucv_sock_close(). This race could cause a NULL pointer dereference when accessing iucv->hs_dev->mtu after hs_dev was set to NULL by iucv_sock_close(), resulting in a kernel crash (NULL pointer dereference oops). The fix involved mirroring the locking strategy used in iucv_sock_setsockopt() by wrapping the entire switch statement in lock_sock()/release_sock() calls and removing a now redundant SO_MSGLIMIT-only lock.
Potential Impact
An attacker with access to AF_IUCV HIPER sockets could trigger a race condition causing a kernel NULL pointer dereference and crash, resulting in a denial of service. There is no indication of privilege escalation or code execution. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code to properly lock the getsockopt handler and prevent the race condition. Users should apply the official kernel updates that include this fix. Since this is not a cloud service, remediation depends on deploying patched kernel versions. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-f6mc-xr5x-m669
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64004"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27aa2a4a8d598912d894
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 19:59:36 UTC
Last updated: 07/20/2026, 21:51:10 UTC
Views: 11
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.