CVE-2026-80635: wifi: wcn36xx: fix OOB read from short trigger BA firmware response
Noroxi assessment
Priority: Monitor (action score 35/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.40% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 04aba50212f9f274e1a726fb3873b5ce8da2d821, af8f0ea1f0a3a5fb5ed2b8fed3f1501d644597ee, b5e6f21923ca89d90256e7346301056f6502691e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 04aba50212f9f274e1a726fb3873b5ce8da2d821, af8f0ea1f0a3a5fb5ed2b8fed3f1501d644597ee, b5e6f21923ca89d90256e7346301056f6502691e 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: wcn36xx: fix OOB read from short trigger BA firmware response The firmware response length is only checked against sizeof(*rsp) (20 bytes), but when candidate_cnt >= 1, a 22-byte candidate struct is read at buf + 20 without verifying the response contains it. This causes an out-of-bounds read of stale heap data, corrupting the BA session state. Add validation that the response includes the candidate data.
- Published
- Aug 28, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 4.7affected
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before 04aba50212f9f274e1a726fb3873b5ce8da2d821affected · git
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before c07aa0534d50361183833e3803204044cf1d0476affected · git
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before d0b57bcd0dac6e2c9a3e474ec280e7db0b3edf35affected · git
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before af8f0ea1f0a3a5fb5ed2b8fed3f1501d644597eeaffected · git
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before d0cafe6ed8d1f6d0097eda31d85f5760d4f359c2affected · git
- 16be1ac55944412e8d132b1db26f994b368c5742 and later · before b5e6f21923ca89d90256e7346301056f6502691eaffected · git
- before 4.7not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-80632Aug 28, 2026 · wifi: mt76: mt7996: Fix NULL pointer dereference in mt7996_init_tx_queues()0Monitor
- ← EarlierCVE-2026-80633Aug 28, 2026 · iommufd: Take dma_resv lock before dma_buf_unpin() in release path35Monitor
- Later →CVE-2026-80636Aug 28, 2026 · netfilter: conntrack: revert ct extension genid infrastructure0Monitor
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 | 04aba50212f9f274e1a726fb3873b5ce8da2d821 | Vendor (CNA) |
| Linux Linux | af8f0ea1f0a3a5fb5ed2b8fed3f1501d644597ee | Vendor (CNA) |
| Linux Linux | b5e6f21923ca89d90256e7346301056f6502691e | Vendor (CNA) |
| Linux Linux | c07aa0534d50361183833e3803204044cf1d0476 | Vendor (CNA) |
| Linux Linux | d0b57bcd0dac6e2c9a3e474ec280e7db0b3edf35 | Vendor (CNA) |
| Linux Linux | d0cafe6ed8d1f6d0097eda31d85f5760d4f359c2 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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.
No dated events beyond publication.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/af8f0ea1f0a3a5fb5ed2b8fed3f1501d644597ee
- git.kernel.org/stable/c/b5e6f21923ca89d90256e7346301056f6502691e
- git.kernel.org/stable/c/c07aa0534d50361183833e3803204044cf1d0476
- git.kernel.org/stable/c/d0b57bcd0dac6e2c9a3e474ec280e7db0b3edf35
- git.kernel.org/stable/c/d0cafe6ed8d1f6d0097eda31d85f5760d4f359c2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.