GHSA-PCCJ-PWWW-VQ83
Vulnerability from github – Published: 2026-10-06 09:31 – Updated: 2026-10-06 09:31In 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
{
"affected": [],
"aliases": [
"CVE-2026-98337"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-06T09:18:26Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: don\u0027t start a ROC while scanning\n\nThe ROC work can be pending when a scan starts (which requires\nROC list to be empty, but that\u0027s possible), and then a new ROC\ncan be added to the list and the work will pick it up.\n\nAvoid starting that ROC if a scan made it between things, as\notherwise we\u0027ll hit a warning later:\n\n WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0\n Workqueue: events_unbound cfg80211_wiphy_work\n Call Trace:\n __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537\n ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193\n cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513",
"id": "GHSA-pccj-pwww-vq83",
"modified": "2026-10-06T09:31:35Z",
"published": "2026-10-06T09:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98337"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/58b806f699052c572dec6cab2c376f884f27e98f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5dc8ec2f8d1d62914661577c23ec151f5c9734a4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/733f0fde95392ed5f61a4e36aee661ea8d0e8581"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/81baab8b645ec532bad2b7a8464191c720ef8fd9"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.