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

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca; < 6f4fc93f76cd8ebd3c89a064573715503048d1ad (affected, git); ≥ fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca; < ddd14d0b5b5e650077779d9a158cb7a80ee8297b (affected, git); ≥ fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca; < 52f5a5ab318f5b120eb686069fbd0108016c02b2 (affected, git); ≥ fb041bb7c0a918b95c6889fc965cdc4a75b4c0ca; < 5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 (affected, git); d0d583484d2ed9f5903edbbfa7e2a68f78b950b0 (affected, git); ≥ 5.4.208; < 5.5 (affected, semver). Source: CNA: Linux
- Linux / Linux: 5.5 (affected); ≥ 0; < 5.5 (unaffected, semver); ≥ 6.12.118; ≤ 6.12.* (unaffected, semver); ≥ 6.18.64; ≤ 6.18.* (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 9.8 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 9.8 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.19%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad (CNA: Linux)

- https://git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b (CNA: Linux)

- https://git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2 (CNA: Linux)

- https://git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 (CNA: Linux)

- https://git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99676; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99676; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99676; retrieved 2026-11-22; source updated Not reported

Revision: 6fdcb607aeb20391d0d67eec2cf0c840a014cc935f5a3f7ca6ac04204b740904

Canonical: https://y2.dev/cve/CVE-2026-99676

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.