CVE Watchtower

CVE-2026-99676Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and

NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Vulnerability Summary

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.
Severity Level
CRITICAL(9.8)
Published Date
Nov 20, 2026
Last Modified
Nov 22, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.17%Probability
Root Weakness (CWE)
N/A
CVSS v3.1 Base Metrics — Score 9.8 (CRITICAL)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and < 6f4fc93f76cd8ebd3c89a064573715503048d1ad
  • Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and < ddd14d0b5b5e650077779d9a158cb7a80ee8297b
  • Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and < 52f5a5ab318f5b120eb686069fbd0108016c02b2
  • Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and < 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2
  • Linux d0d583484d2ed9f5903edbbfa7e2a68f78b950b0
  • Linux >= 5.4.208 and < 5.5
  • Linux 5.5
Patched Versions
  • Linux 6f4fc93f76cd8ebd3c89a064573715503048d1ad
  • Linux ddd14d0b5b5e650077779d9a158cb7a80ee8297b
  • Linux 52f5a5ab318f5b120eb686069fbd0108016c02b2
  • Linux 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2
  • Linux 5.5

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 20, 2026Published
  • Nov 22, 2026Record last modified
  • Nov 22, 2026CVSS score changed: 0.0 to 9.8
  • Nov 22, 2026Severity changed to CRITICAL

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Linux >= fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca and CVEsYou are reading CVE-2026-99676. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 22, 2026 12:25 UTC