net: restore refcount ordering for lockless socket access
Summary
| CVE | CVE-2026-99676 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:02 UTC |
| Updated | 2026-11-22 11:17:05 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 9.8 CRITICAL from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001680000 probability, percentile 0.061890000 (date 2026-11-21)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca 6f4fc93f76cd8ebd3c89a064573715503048d1ad git | Not specified |
| CNA | Linux | Linux | affected fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca ddd14d0b5b5e650077779d9a158cb7a80ee8297b git | Not specified |
| CNA | Linux | Linux | affected fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca 52f5a5ab318f5b120eb686069fbd0108016c02b2 git | Not specified |
| CNA | Linux | Linux | affected fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 git | Not specified |
| CNA | Linux | Linux | affected d0d583484d2ed9f5903edbbfa7e2a68f78b950b0 git | Not specified |
| CNA | Linux | Linux | affected 5.4.208 5.5 semver | Not specified |
| CNA | Linux | Linux | affected 5.5 | Not specified |
| CNA | Linux | Linux | unaffected 5.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.118 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.64 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3.5 7.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.4-rc2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.