CVE-2026-68409
Last modified
CVE-2026-68409 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: defer link RX stats percpu free to RCU sta_remove_link() frees a removed MLO link's RX stats percpu buffer right away, but defers only the link container to RCU: sta_info_free_link(&alloc->info); kfree_rcu(alloc, rcu_head); The RX fast path reads link_sta under rcu_read_lock and writes the percpu stats. A reader that resolved link_sta before the removal keeps the pointer.
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: defer link RX stats percpu free to RCU sta_remove_link() frees a removed MLO link's RX stats percpu buffer right away, but defers only the link container to RCU: sta_info_free_link(&alloc->info); kfree_rcu(alloc, rcu_head); The RX fast path reads link_sta under rcu_read_lock and writes the percpu stats. A reader that resolved link_sta before the removal keeps the pointer. The container stays alive from the kfree_rcu, so the read still works. But the percpu block it points to is already freed. This needs uses_rss. That is when pcpu_rx_stats exists. The full STA teardown frees the deflink stats only after synchronize_net(). The link removal path had no such barrier. The race is hard to win in practice, but the free should still wait for RCU. Free the link together with its data from a single RCU callback, so the percpu block is reclaimed only after readers drain.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c71420db653aba30a234d1e4cf86dde376e604fa, < 2aa1789880fa5e41049b0f6a74a4fc2fa1997610; >= c71420db653aba30a234d1e4cf86dde376e604fa, < a03fceae0c65b31ce31840dac5e26684ceecb65b; >= c71420db653aba30a234d1e4cf86dde376e604fa, < aa2eb62525188269cdd402a583b9a8ed94657ff0 |
| Linux | Linux | 6.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68409?
How severe is CVE-2026-68409?
How do I fix CVE-2026-68409?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68403In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68404In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68405In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68406In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68407In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68408In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6841Request Tracker is vulnerable to a reflected cross-site scri…6.1
- CVE-2026-68410In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68411In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68412In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68413In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68414In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68409?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
