wifi: wcn36xx: fix heap overflow from oversized firmware HAL response
In the Linux kernel, the following vulnerability has been resolved: wifi: wcn36xx: fix heap overflow from oversized firmware HAL response The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content. Add a bounds check on the response length.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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.5%
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.13affected
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before dae9cadf0925f1cbfb71306d60490890df3870a6affected · git
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before cfc67aee0c83e7f5d43a1dad3e25c789e9cc1d92affected · git
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before 15545ee71301e82d26d9a31b407ed0019eb62a60affected · git
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before 1b5d8a248c3afa640bcc99fa95abcd1e36f3ee18affected · git
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before 18813b90032bfaafb225906a4d2b51be4dfc02c3affected · git
- 8e84c25821698bdef73c0329fb2022a4673b7adc and later · before 88a240d86d3d64521f9194abe185ac71cc74d0bdaffected · git
- before 3.13not 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 15545ee71301e82d26d9a31b407ed0019eb62a60 | Vendor (CNA) |
| Linux Linux | 18813b90032bfaafb225906a4d2b51be4dfc02c3 | Vendor (CNA) |
| Linux Linux | 1b5d8a248c3afa640bcc99fa95abcd1e36f3ee18 | Vendor (CNA) |
| Linux Linux | 88a240d86d3d64521f9194abe185ac71cc74d0bd | Vendor (CNA) |
| Linux Linux | cfc67aee0c83e7f5d43a1dad3e25c789e9cc1d92 | Vendor (CNA) |
| Linux Linux | dae9cadf0925f1cbfb71306d60490890df3870a6 | 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).
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
- git.kernel.org/stable/c/15545ee71301e82d26d9a31b407ed0019eb62a60
- git.kernel.org/stable/c/18813b90032bfaafb225906a4d2b51be4dfc02c3
- git.kernel.org/stable/c/1b5d8a248c3afa640bcc99fa95abcd1e36f3ee18
- git.kernel.org/stable/c/88a240d86d3d64521f9194abe185ac71cc74d0bd
- git.kernel.org/stable/c/cfc67aee0c83e7f5d43a1dad3e25c789e9cc1d92
- git.kernel.org/stable/c/dae9cadf0925f1cbfb71306d60490890df3870a6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.