0.0
NA
CVE-2026-68409
wifi: mac80211: defer link RX stats percpu free to RCU
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.

INFO

Published Date :

Aug. 10, 2026, 1:20 p.m.

Last Modified :

Aug. 10, 2026, 1:20 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-68409 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Free RX stats percpu buffer after RCU to prevent race conditions.
  • Defer RX stats percpu buffer free to RCU.
  • Ensure the link container and its data are freed in a single RCU callback.
  • Reclaim the percpu block after readers have drained.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-68409.

URL Resource
https://git.kernel.org/stable/c/2aa1789880fa5e41049b0f6a74a4fc2fa1997610
https://git.kernel.org/stable/c/a03fceae0c65b31ce31840dac5e26684ceecb65b
https://git.kernel.org/stable/c/aa2eb62525188269cdd402a583b9a8ed94657ff0
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-68409 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-68409 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-68409 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-68409 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 10, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'c71420db653aba30a234d1e4cf86dde376e604fa', 'lessThan': '2aa1789880fa5e41049b0f6a74a4fc2fa1997610', 'versionType': 'git'}, {'status': 'affected', 'version': 'c71420db653aba30a234d1e4cf86dde376e604fa', 'lessThan': 'a03fceae0c65b31ce31840dac5e26684ceecb65b', 'versionType': 'git'}, {'status': 'affected', 'version': 'c71420db653aba30a234d1e4cf86dde376e604fa', 'lessThan': 'aa2eb62525188269cdd402a583b9a8ed94657ff0', 'versionType': 'git'}], 'programFiles': ['net/mac80211/sta_info.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.0'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.0', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc4', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/mac80211/sta_info.c'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/2aa1789880fa5e41049b0f6a74a4fc2fa1997610
    Added Reference https://git.kernel.org/stable/c/a03fceae0c65b31ce31840dac5e26684ceecb65b
    Added Reference https://git.kernel.org/stable/c/aa2eb62525188269cdd402a583b9a8ed94657ff0
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.