CVE-2026-99676
Severity unknownNo known exploitationFix availablenet: restore refcount ordering for lockless socket access
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 5.4.208 before 5.5 | 5.5 | CVE Program |
| Linux | Linux | from fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before ddd14d0b5b5e650077779d9a158cb7a80ee8297b | ddd14d0b5b5e650077779d9a158cb7a80ee8297b | CVE Program |
| Linux | Linux | from fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 52f5a5ab318f5b120eb686069fbd0108016c02b2 | 52f5a5ab318f5b120eb686069fbd0108016c02b2 | CVE Program |
| Linux | Linux | from fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 | 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 | CVE Program |
| Linux | Linux | from fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca before 6f4fc93f76cd8ebd3c89a064573715503048d1ad | 6f4fc93f76cd8ebd3c89a064573715503048d1ad | CVE Program |
| Linux | Linux | 5.5 | Not documented | CVE Program |
| Linux | Linux | d0d583484d2ed9f5903edbbfa7e2a68f78b950b0 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.5 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2 (opens in a new tab)
- https://git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 (opens in a new tab)
- https://git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad (opens in a new tab)
- https://git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b (opens in a new tab)