data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-64004 in the interactive tracker

CVE-2026-64004

net/iucv: fix locking in .getsockopt

7.8 EPSS 0.1% AV:L

Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem net/iucv. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-64004 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixed6.1.176-1Update the kernel and reboot. Fixed in 6.1.176-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.94-1Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.0.12-1Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.0.12-1Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

net/iucv/af_iucv.c

What this is
S390 IUCV NETWORK LAYERMAINTAINERS section matched on net/iucv/ · linux-s390@vger.kernel.org · Supported
Kernel module
af_iucv

Check it on the machine

grep -wE 'CONFIG_AFIUCV|CONFIG_IUCV' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w af_iucv

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian does not build this code in 1 release. It does build it in 3 releases, so the answer depends on which release the machine runs.

  • bookwormn
  • trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64
  • forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64
n
not enabled on any flavour - this release does not build the code
M
a module where it is built at all; some flavours do not build it
Build switches
CONFIG_AFIUCV, CONFIG_IUCV
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-07-19 (3 months ago)source
CVSS
7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
local (AV:L)source
EPSS
0.10%, higher than 0.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
net/iucv

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
3.45.10.259884eb247b74d
3.45.15.21045bb8de8c95d
3.46.1.1761fc30bd4e55e
3.46.6.143cd691beafea0
3.46.12.936e792b8dd300
3.46.18.35981736924338
3.47.0.1269554adc7a6f
3.47.13589d20a666c

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:LAttack vector, local
The flaw is reached through the getsockopt(2) syscall on an AF_IUCV HIPER socket; the generic socket layer does not acquire the socket lock before calling iucv_sock_getsockopt(), so exploitation requires local access to the socket file descriptor.
AC:LAttack complexity, low
The attacker controls both sides of the race by running concurrent getsockopt(SO_MSGSIZE) and recvmsg()/close() threads on the same socket, making the window reliably winnable without external timing luck.
PR:LPrivileges required, low
The fix commit explicitly states any AF_IUCV HIPER user can trigger the crash, and iucv_sock_create imposes no capability or root requirement beyond creating and binding a HiperSockets AF_IUCV socket on s390.
UI:NUser interaction, none
Exploitation requires no action from any other user; the attacker races their own syscalls on a socket they control.
S:UScope, unchanged
The impact is a kernel oops or crash within the same kernel security boundary, with no cross-VM, cross-container, or IOMMU boundary crossing.
C:HConfidentiality impact, high
The unlocked TOCTOU between the hs_dev NULL check and dereference races with dev_put() freeing the net_device, creating a use-after-free read whose mtu field is copied to userspace via copy_to_user.
I:HIntegrity impact, high
Use-after-free on a freed net_device structure in kernel heap memory is a memory corruption primitive that could be further leveraged for control-flow hijacking, and per kernel CVSS guidance UAF bugs warrant High integrity impact.
A:HAvailability impact, high
Successful exploitation produces a NULL pointer dereference oops or kernel panic, causing complete loss of availability on the affected IBM Z LPAR or guest.