Threat Feed

CVE-2026-99676: net: restore refcount ordering for lockless socket access

Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: net: restore refcount ordering for lockless socket access Before commit fb041bb7c0a9 ("locking/refcount: Consolidate implementations of refcount_t"), default builds implemented refcount_inc_not_zero() using atomic_add_unless(), which provided full memory ordering on success. The commit removed that ordering on weakly ordered architectures, allowing accesses after a successful reference acquisition to be reordered before it. Use refcount_inc_not_zero_acquire() in the IPv4 and IPv6 established lookups and in inet_twsk_purge(), where the socket is validated again after taking a reference. bpf_sk_assign() can receive a socket pointer obtained through BTF without a reference. Use acquire ordering when it takes its own reference for a refcounted socket. Use refcount_set_release() when setting refcounts in the SYN cookie, TCP Fast Open, request migration, and TIME_WAIT paths. Keep the existing TIME_WAIT smp_wmb(), which separately orders the refcount store before ehash publication.

Enclave's analysis

This patches a dropped memory-ordering guarantee in how the Linux kernel looks up TCP sockets, letting one CPU reuse a freed socket or route while another CPU is still mid-lookup on it. An attacker who can reach a TCP listener and churn connections hard enough could in theory race that gap into a kernel crash or worse. No public PoC, no in-the-wild use, and the one independent vendor review calls it a crash-only bug, not remote code execution. Just take the kernel update when it ships.

Fix

Upgrade Linux kernel to 6.12.118, 6.18.64, 7.3.5, or mainline 7.4-rc2 depending on branch. No fixed version is listed for Linux; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
Linuxfb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 6f4fc93f76cd8ebd3c89a064573715503048d1adNot listed
Linuxfb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before ddd14d0b5b5e650077779d9a158cb7a80ee8297bNot listed
Linuxfb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 52f5a5ab318f5b120eb686069fbd0108016c02b2Not listed
Linuxfb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2Not listed
Linuxd0d583484d2ed9f5903edbbfa7e2a68f78b950b0Not listed
Linux5.4.208 before 5.5Not listed
Linux5.5Not listed
Linux kernel5.5 up to the point before fixes landed in each branch6.12.118, 6.18.64, 7.3.5, or mainline 7.4-rc2 depending on branch

Seen in 2 sources