CVE-2025-39750
What it is
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.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel < 6.6.103
- Linux Kernel < 6.12.43
- Linux Kernel < 6.15.11
- Linux Kernel < 6.16.2
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-39750.md and follow it. Check whether this project is affected by CVE-2025-39750. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2ef17d1476ab26bce89764e2f16833d7f52acc38
- https://git.kernel.org/stable/c/30cad87978057516c93467516bc481a3eacfd66a
- https://git.kernel.org/stable/c/4a2bf707270f897ab8077baee8ed5842a5321686
- https://git.kernel.org/stable/c/6301fe4f209165334d251a1c6da8ae47f93cb32c
- https://git.kernel.org/stable/c/907c630e58af9e86e215f3951c7b287bd86d0f15
References
- https://git.kernel.org/stable/c/2ef17d1476ab26bce89764e2f16833d7f52acc38
- https://git.kernel.org/stable/c/30cad87978057516c93467516bc481a3eacfd66a
- https://git.kernel.org/stable/c/4a2bf707270f897ab8077baee8ed5842a5321686
- https://git.kernel.org/stable/c/6301fe4f209165334d251a1c6da8ae47f93cb32c
- https://git.kernel.org/stable/c/907c630e58af9e86e215f3951c7b287bd86d0f15