CVE-2025-68729: wifi: ath12k: Fix MSDU buffer types handling in RX error path
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 17a9b93283c6f0b799a338bbc50fa115012429d9, 36f9edbb9d0fc36c865c74f3c1ad8e1261ad3981, 5ff5a9d71cdc49c3400f30583a784ad0a17d01ec.
Low priority for now. Upgrade to Linux Linux 17a9b93283c6f0b799a338bbc50fa115012429d9, 36f9edbb9d0fc36c865c74f3c1ad8e1261ad3981, 5ff5a9d71cdc49c3400f30583a784ad0a17d01ec 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: ath12k: Fix MSDU buffer types handling in RX error path Currently, packets received on the REO exception ring from unassociated peers are of MSDU buffer type, while the driver expects link descriptor type packets. These packets are not parsed further due to a return check on packet type in ath12k_hal_desc_reo_parse_err(), but the associated skb is not freed. This may lead to kernel crashes and buffer leaks. Hence to fix, update the RX error handler to explicitly drop MSDU buffer type packets received on the REO exception ring. This prevents further processing of invalid packets and ensures stability in the RX error handling path. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1
- Published
- Dec 24, 2025
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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.3affected
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before abfbceda0d2391524ad1df88867b3f3af36d17c7affected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 17a9b93283c6f0b799a338bbc50fa115012429d9affected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 5ff5a9d71cdc49c3400f30583a784ad0a17d01ecaffected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before ab0554f51e5f2b9506e8a09e8accd02f00056729affected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 36f9edbb9d0fc36c865c74f3c1ad8e1261ad3981affected · git
- before 6.3not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.17.13 and later · up to and including 6.17.*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-6.12 | before 6.12.115-2~deb12u1 | 6.12.115-2~deb12u1 |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-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-2025-68727Dec 24, 2025 · ntfs3: Fix uninit buffer allocated by __getname()0Monitor
- ← EarlierCVE-2025-68728Dec 24, 2025 · ntfs3: fix uninit memory after failed mi_read in mi_format_new0Monitor
- Later →CVE-2025-68730Dec 24, 2025 · accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context()31Monitor
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 | 17a9b93283c6f0b799a338bbc50fa115012429d9 | Vendor (CNA) |
| Linux Linux | 36f9edbb9d0fc36c865c74f3c1ad8e1261ad3981 | Vendor (CNA) |
| Linux Linux | 5ff5a9d71cdc49c3400f30583a784ad0a17d01ec | Vendor (CNA) |
| Linux Linux | ab0554f51e5f2b9506e8a09e8accd02f00056729 | Vendor (CNA) |
| Linux Linux | abfbceda0d2391524ad1df88867b3f3af36d17c7 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 6.17.13-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~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.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.