CVE-2026-98337
wifi: mac80211: don't start a ROC while scanning
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ aaa016ccd5df89d73483d0d51ee1f692978ccc35, < 5dc8ec2f8d1d62914661577c23ec151f5c9734a4Upgrade to: 5dc8ec2f8d1d62914661577c23ec151f5c9734a4Affected: ≥ aaa016ccd5df89d73483d0d51ee1f692978ccc35, < 81baab8b645ec532bad2b7a8464191c720ef8fd9Upgrade to: 81baab8b645ec532bad2b7a8464191c720ef8fd9Affected: ≥ aaa016ccd5df89d73483d0d51ee1f692978ccc35, < 58b806f699052c572dec6cab2c376f884f27e98fUpgrade to: 58b806f699052c572dec6cab2c376f884f27e98fAffected: ≥ aaa016ccd5df89d73483d0d51ee1f692978ccc35, < 733f0fde95392ed5f61a4e36aee661ea8d0e8581Upgrade to: 733f0fde95392ed5f61a4e36aee661ea8d0e8581Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't start a ROC while scanning The ROC work can be pending when a scan starts (which requires ROC list to be empty, but that's possible), and then a new ROC can be added to the list and the work will pick it up. Avoid starting that ROC if a scan made it between things, as otherwise we'll hit a warning later: WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0 Workqueue: events_unbound cfg80211_wiphy_work Call Trace: __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537 ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193 cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/5dc8ec2f8d1d62914661577c23ec151f5c9734a4
- git.kernel.org/stable/c/81baab8b645ec532bad2b7a8464191c720ef8fd9
- git.kernel.org/stable/c/58b806f699052c572dec6cab2c376f884f27e98f
And 1 more reference. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI