CVE-2026-98702: wifi: mac80211: reject invalid 320 MHz CSA bandwidth
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 1892e71aa2e5ee667d87c6e49e3661f5e290303b, 56e236759f0a8dc910c2ae7cd3c161f298ee5794, 79b3ce0d881cd6e5d4d3496b19f5cc5e7089a56c.
Low priority for now. Upgrade to Linux Linux 1892e71aa2e5ee667d87c6e49e3661f5e290303b, 56e236759f0a8dc910c2ae7cd3c161f298ee5794, 79b3ce0d881cd6e5d4d3496b19f5cc5e7089a56c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: reject invalid 320 MHz CSA bandwidth The HT/VHT channel definition validator can receive a 320 MHz bandwidth indication from a received CSA frame on a non-6 GHz link. It warns for this unsupported width but continues with an uninitialized vht_operation.chan_width, which is then read by ieee80211_chandef_vht_oper(). With panic_on_warn enabled, this lets a received frame panic the kernel. Reject the channel definition before entering the VHT operation conversion. This preserves the existing CSA fallback while avoiding both the warning and the uninitialized read.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.9affected
- 21c3f8f95554feff9bed15703e89adbe582e0383 and later · before cf0ddacce173890407ed3fa50c8ea9b3c0cc0e16affected · git
- 21c3f8f95554feff9bed15703e89adbe582e0383 and later · before 1892e71aa2e5ee667d87c6e49e3661f5e290303baffected · git
- 21c3f8f95554feff9bed15703e89adbe582e0383 and later · before 79b3ce0d881cd6e5d4d3496b19f5cc5e7089a56caffected · git
- 21c3f8f95554feff9bed15703e89adbe582e0383 and later · before 56e236759f0a8dc910c2ae7cd3c161f298ee5794affected · git
- before 6.9not affected · semver
- 6.12.113 and later · up to and including 6.12.*not affected · semver
- 6.18.56 and later · up to and including 6.18.*not affected · semver
- 7.2.10 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98700Oct 18, 2026 · wifi: mac80211: set info->band for 802.3 encap offload frames0Monitor
- ← EarlierCVE-2026-98701Oct 18, 2026 · wifi: mac80211: release mesh path quota on failed additions0Monitor
- Later →CVE-2026-98703Oct 18, 2026 · wifi: mac80211: minstrel_ht: validate fixed rate index0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1892e71aa2e5ee667d87c6e49e3661f5e290303b | Vendor (CNA) |
| Linux Linux | 56e236759f0a8dc910c2ae7cd3c161f298ee5794 | Vendor (CNA) |
| Linux Linux | 79b3ce0d881cd6e5d4d3496b19f5cc5e7089a56c | Vendor (CNA) |
| Linux Linux | cf0ddacce173890407ed3fa50c8ea9b3c0cc0e16 | Vendor (CNA) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+19 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.