CVE-2026-74561: Use-after-free in Linux kernel nexthop replacement
- Vendor
- Linux
A race condition in the Linux kernel's nexthop handling causes a slab use-after-free in nh_rt_cache_flush(). During RTNL-serialized nexthop replacement, the function traverses nh->f6i_list without holding nh->lock. Concurrent IPv6 route additions or deletions modify that list under nh->lock and can free fib6_info entries while the traversal still references them. The traversal updates route serial numbers through fib6_update_sernum_upto_root(), which requires tb6_lock; simply acquiring nh->lock around the traversal would invert the established tb6_lock-to-nh->lock ordering and risk deadlock. The race can result in reads from freed kernel memory.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Concurrent nexthop replacement and IPv6 route modification can trigger a kernel use-after-free read, demonstrated by a KASAN report. Kernel crashes and denial of service are possible. Privilege escalation, arbitrary code execution, and other exploitation outcomes have not been established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Until patched kernels can be deployed, reduce exposure by restricting the ability to perform nexthop and routing-table modifications to trusted privileged administrators only, minimizing opportunities to trigger the vulnerable replacement path concurrently with IPv6 route updates. Limiting untrusted access to netlink-based network configuration interfaces and reducing unnecessary IPv6 routing churn may lower the likelihood of exploitation, but these measures do not fully eliminate the underlying race condition.
Remediation
Patch, then assume compromise.
Apply the upstream Linux kernel fix or a distribution kernel update containing it. The fix replaces the per-route IPv6 serial-number updates in nh_rt_cache_flush() with rt_genid_bump_ipv6(), invalidating cached destinations throughout the network namespace without traversing nh->f6i_list. Do not merely add nh->lock around the existing traversal, as this would introduce a lock-order inversion and possible deadlock. Fixed kernel versions are not specified.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-74561 exploited in the wild?
- As of Nov 12, 2026, Mallory has no reports of CVE-2026-74561 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-74561?
- As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-74561.
- Is there a patch for CVE-2026-74561?
- Apply the upstream Linux kernel fix or a distribution kernel update containing it. The fix replaces the per-route IPv6 serial-number updates in nh_rt_cache_flush() with rt_genid_bump_ipv6(), invalidating cached destinations throughout the network namespace without traversing nh->f6i_list.
- What products are affected by CVE-2026-74561?
- Linux Kernel.
- How severe is CVE-2026-74561?
- CVE-2026-74561 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.11% (2nd percentile) as of Nov 12, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.