AI Science Tracker

Linux TCP congestion-control pointer is dereferenced without RCU protection

Linux kernel · AI involvement attributed to Microsoft MDASH

Finding and attribution

Two TCP getsockopt paths access the same congestion-control object without protecting its lifetime. Concurrent replacement of dynamically allocated BPF congestion-control state can leave stale accesses to its function pointer or name. The two CVEs are grouped as one missing-synchronization root while retaining their separate fixes.

Product: Linux kernel. AI system: Microsoft MDASH. Team / organization: Microsoft FORGE Lab.

CVE identifiers: CVE-2026-99138, CVE-2026-99139.

AI and human contribution (source account): Microsoft explicitly lists this CVE in its MDASH campaign. The campaign combined model-assisted scanning, reproduction agents and expert root-cause review; a particular model is not individually assigned to this case, and autonomous or sole discovery is not established.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The Linux CNA publicly documents the issue and fix. The reviewed sources do not establish exploitation before disclosure.

Remediation status: fix documented. Protect both accesses with RCU, use explicit pointer loads and copy the name before leaving the protected section. The CNA records upstream fixes; branch-specific availability and installed remediation are not established here. Both linked CVE patch paths remain relevant.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 28 Oct 2026. AI attribution dated 11 Nov 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: other.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

CVE-2026-99138, CVE-2026-99139: other.
Prerequisites / affected scope: Requires the affected TCP information or congestion-name query racing with replacement or release of dynamic BPF congestion-control state..
Exploitation evidence: The CNA establishes the stated technical effect; no in-the-wild exploitation is established in the reviewed material.. Impact source · checked 16 Nov 2026.

Documented fix: Protect both accesses with RCU, use explicit pointer loads and copy the name before leaving the protected section. The CNA records upstream fixes; branch-specific availability and installed remediation are not established here. Both linked CVE patch paths remain relevant.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases