CVE-2025-39750: wifi: ath12k: Correct tid cleanup when tid setup fails
Noroxi assessment
Priority: Monitor (action score 28/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.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2ef17d1476ab26bce89764e2f16833d7f52acc38, 30cad87978057516c93467516bc481a3eacfd66a, 4a2bf707270f897ab8077baee8ed5842a5321686.
Low priority for now. Upgrade to Linux Linux 2ef17d1476ab26bce89764e2f16833d7f52acc38, 30cad87978057516c93467516bc481a3eacfd66a, 4a2bf707270f897ab8077baee8ed5842a5321686 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: Correct tid cleanup when tid setup fails Currently, if any error occurs during ath12k_dp_rx_peer_tid_setup(), the tid value is already incremented, even though the corresponding TID is not actually allocated. Proceed to ath12k_dp_rx_peer_tid_delete() starting from unallocated tid, which might leads to freeing unallocated TID and cause potential crash or out-of-bounds access. Hence, fix by correctly decrementing tid before cleanup to match only the successfully allocated TIDs. Also, remove tid-- from failure case of ath12k_dp_rx_peer_frag_setup(), as decrementing the tid before cleanup in loop will take care of this. Compile tested only.
- Published
- Sep 11, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 8.8
- 1.7 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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 30cad87978057516c93467516bc481a3eacfd66aaffected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 2ef17d1476ab26bce89764e2f16833d7f52acc38affected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 907c630e58af9e86e215f3951c7b287bd86d0f15affected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 6301fe4f209165334d251a1c6da8ae47f93cb32caffected · git
- d889913205cf7ebda905b1e62c5867ed4e39f6c2 and later · before 4a2bf707270f897ab8077baee8ed5842a5321686affected · git
- before 6.3not affected · semver
- 6.6.103 and later · up to and including 6.6.*not affected · semver
- 6.12.43 and later · up to and including 6.12.*not affected · semver
- 6.15.11 and later · up to and including 6.15.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.3 and later · before 6.6.103
- linux linux kernel6.7 and later · before 6.12.43
- linux linux kernel6.13 and later · before 6.15.11
- linux linux kernel6.16 and later · before 6.16.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39748Sep 11, 2025 · bpf: Forget ranges when refining tnum after JSET22Monitor
- ← EarlierCVE-2025-39749Sep 11, 2025 · rcu: Protect ->defer_qs_iw_pending from data race28Monitor
- Later →CVE-2025-39752Sep 11, 2025 · ARM: rockchip: fix kernel hang during smp initialization22Monitor
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 | 2ef17d1476ab26bce89764e2f16833d7f52acc38 | Vendor (CNA) |
| Linux Linux | 30cad87978057516c93467516bc481a3eacfd66a | Vendor (CNA) |
| Linux Linux | 4a2bf707270f897ab8077baee8ed5842a5321686 | Vendor (CNA) |
| Linux Linux | 6301fe4f209165334d251a1c6da8ae47f93cb32c | Vendor (CNA) |
| Linux Linux | 907c630e58af9e86e215f3951c7b287bd86d0f15 | Vendor (CNA) |
| debian:linux | 6.12.43-1 · Debian:13 | 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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- SSVC exploitation— → none
- 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.