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

> A flaw in the ath12k WiFi driver causes out-of-bounds access when TID setup fails, potentially leading to a system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-39750, DEBIAN-CVE-2025-39750, GHSA-q522-2v7v-4rm7, ROOT-OS-DEBIAN-11-CVE-2025-39750, ROOT-OS-DEBIAN-12-CVE-2025-39750, ROOT-OS-UBUNTU-2204-CVE-2025-39750, ROOT-OS-UBUNTU-2404-CVE-2025-39750, UBUNTU-CVE-2025-39750

## What is CVE-2025-39750?

CVE-2025-39750 is a high-severity memory corruption vulnerability in Linux kernel, published on 11 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-39750?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-39750?

Apply the vendor's patch.

## Is CVE-2025-39750 being exploited?

There is no known exploitation of CVE-2025-39750 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-39750 and fix it if it is affected.

What it is: CVE-2025-39750 is a high-severity memory corruption vulnerability in Linux kernel, published on 11 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-39750 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-39750/ (Markdown: https://insights.sbomify.com/CVE-2025-39750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-39750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-39750
- OSV: https://osv.dev/vulnerability/CVE-2025-39750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-39750/
Summaries are generated and may contain mistakes; the official description above is the record.