CVE-2026-98708: wifi: mac80211: keep paired old chanctx alive
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 026ae72fa6d0f7e04951441026be473f22911b87, 0fba8fbf5ab0bffc1866e5038aaab772d31d1584, 1c82d0c5d509179ba2a4edfa096f516aebf960b0; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 026ae72fa6d0f7e04951441026be473f22911b87, 0fba8fbf5ab0bffc1866e5038aaab772d31d1584, 1c82d0c5d509179ba2a4edfa096f516aebf960b0; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 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: keep paired old chanctx alive An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx. That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer. Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th 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
- 3.17affected
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 026ae72fa6d0f7e04951441026be473f22911b87affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 624bf5338d8c2f55db455ce4f2543ca4a83fab03affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 0fba8fbf5ab0bffc1866e5038aaab772d31d1584affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 47864a9092fd6f6b3f312d1e5b233ecdc68b1bd8affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 21a688cbeae0e682f03e91f1e7a7eedd60d9d4f2affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 1c82d0c5d509179ba2a4edfa096f516aebf960b0affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before afd1cdd16a25c7185b812a612ab7d5f2cbd1e086affected · git
- 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and later · before 3412e9a800786d1dec4a58367db1cba275e7ef11affected · git
- before 3.17not affected · semver
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 | from 0 | — |
| 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-98706Oct 18, 2026 · wifi: mac80211: drain PS delivery work during station teardown0Monitor
- ← EarlierCVE-2026-98707Oct 18, 2026 · wifi: mac80211: shut down RX BA session timer on teardown0Monitor
- Later →CVE-2026-98709Oct 18, 2026 · wifi: mac80211: count only matching reservations in reserved switch0Monitor
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 | 026ae72fa6d0f7e04951441026be473f22911b87 | Vendor (CNA) |
| Linux Linux | 0fba8fbf5ab0bffc1866e5038aaab772d31d1584 | Vendor (CNA) |
| Linux Linux | 1c82d0c5d509179ba2a4edfa096f516aebf960b0 | Vendor (CNA) |
| Linux Linux | 21a688cbeae0e682f03e91f1e7a7eedd60d9d4f2 | Vendor (CNA) |
| Linux Linux | 3412e9a800786d1dec4a58367db1cba275e7ef11 | Vendor (CNA) |
| Linux Linux | 47864a9092fd6f6b3f312d1e5b233ecdc68b1bd8 | Vendor (CNA) |
| Linux Linux | 624bf5338d8c2f55db455ce4f2543ca4a83fab03 | Vendor (CNA) |
| Linux Linux | afd1cdd16a25c7185b812a612ab7d5f2cbd1e086 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| 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 (7 more)Show less
- git.kernel.org/stable/c/0fba8fbf5ab0bffc1866e5038aaab772d31d1584
- git.kernel.org/stable/c/1c82d0c5d509179ba2a4edfa096f516aebf960b0
- git.kernel.org/stable/c/21a688cbeae0e682f03e91f1e7a7eedd60d9d4f2
- git.kernel.org/stable/c/3412e9a800786d1dec4a58367db1cba275e7ef11
- git.kernel.org/stable/c/47864a9092fd6f6b3f312d1e5b233ecdc68b1bd8
- git.kernel.org/stable/c/624bf5338d8c2f55db455ce4f2543ca4a83fab03
- git.kernel.org/stable/c/afd1cdd16a25c7185b812a612ab7d5f2cbd1e086
Vendor advisories and official records. Exploit/PoC links are deliberately left out.