AI Science Tracker

Linux nexthop replacement races with IPv6 route deletion during f6i_list walks

Linux kernel · AI involvement attributed to Microsoft MDASH

Finding and attribution

RTNL-serialized nexthop replacement walks nh->f6i_list without nh->lock while route add/delete mutates and frees fib6_info entries under that lock, causing a use-after-free. Related CVE-2026-74562 is grouped here as a shared-root issue; its separate call sites and fixes are documented in the case evidence. The linked CVE-2026-74562 describes additional replacement-time walks of the same list without the same lock; the campaign notes group the linked notices under the shared missing-synchronization invariant and preserve both fixes.

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

CVE identifiers: CVE-2026-74561, CVE-2026-74562.

AI and human contribution (source account): The first-party Microsoft MDASH report and its linked CVE cohort list identify CVE-2026-74561 as a campaign finding. Microsoft states MDASH scanned Linux subsystems using named AI models. Its selected-findings report documents lab-confirmed local-root exploits for listed cases. The linked Microsoft cohort list includes both CVE-2026-74561 and CVE-2026-74562; campaign attribution applies to the grouped issue.

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 cited public CVE notice is the disclosure. The sources checked here do not establish whether exploitation preceded disclosure.

Remediation status: fix documented. Take nh->lock around affected list walks; retain both linked CVE identifiers and patch paths. Fixed-version and downstream deployment status should be checked with the relevant Linux distribution; the upstream fix does not establish deployed remediation.

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 15 Aug 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, privilege escalation.

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-74561, CVE-2026-74562: other.
Prerequisites / affected scope: CNA documents KASAN use-after-free on freed fib6_info during concurrent route deletion. Required operations are local RTNETLINK configuration. Microsoft identifies the shared cohort’s lab-confirmed local-root exploit status; not in-the-wild exploitation..
Exploitation evidence: No claim of in-the-wild exploitation is made; retain only the source-described technical effect and controlled-lab claim where stated.. Impact source · checked 16 Nov 2026.

CVE-2026-74561, CVE-2026-74562: privilege escalation.
Prerequisites / affected scope: Microsoft FORGE reports confirmed local root privilege-escalation exploits for this CVE among eight listed Linux findings in controlled laboratory environments. The article says some cases required non-default settings or disabled exploit mitigations, but does not map those prerequisites to this individual CVE..
Exploitation evidence: Microsoft says working local root privilege-escalation exploits were confirmed in controlled laboratory environments; the article does not report in-the-wild exploitation.. Impact source · checked 16 Nov 2026.

Documented fix: Take nh->lock around affected list walks; retain both linked CVE identifiers and patch paths. Fixed-version and downstream deployment status should be checked with the relevant Linux distribution; the upstream fix does not establish deployed remediation.

Original evidence

Download this source record (JSON)

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