CVE-2025-39750 [High] | Out-of-bounds Read in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-09-12	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-09-12

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.2

[email protected]

OS Trackers for CVE-2025-39750

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-39750 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-39750
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-39750
`suse`	high	CVE-2025-39750 severity important: SUSE including 469 source package names (2.1.3-6.80:kernel-default-base-6.4.0-35.1.21.12, 2.1.3-7.57:kernel-default-6.4.0-35.1, …), 1068 product×package rows across 212 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (212 product lines)): Fixed 619, Known Affected 231, Known Not Affected 197, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-39750/
`ubuntu`	medium	CVE-2025-39750 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 180, released 118, needed 80, not-affected 16, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-39750

Affected software / configurations for CVE-2025-39750

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.3, < 6.6.103	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.43	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.11	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.16, < 6.16.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2025-39750

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

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2025-39750

Common vulnerability scoring system (CVSS) metrics for CVE-2025-39750

Weakness enumeration for CVE-2025-39750

OS Trackers for CVE-2025-39750

Affected software / configurations for CVE-2025-39750

References for CVE-2025-39750