Linux: Out-of-bounds Read
CVE-2025-39750 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 30cad87978057516c93467516bc481a3eacfd66a, 2ef17d1476ab26bce89764e2f16833d7f52acc38, 907c630e58af9e86e215f3951c7b287bd86d0f15 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 30cad87978057516c93467516bc481a3eacfd66a or 2ef17d1476ab26bce89764e2f16833d7f52acc38 or 907c630e58af9e86e215f3951c7b287bd86d0f15 or 6301fe4f209165334d251a1c6da8ae47f93cb32c, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.103 or 6.12.43 or 6.15.11 or 6.16.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 30cad87978057516c93467516bc481a3eacfd66a; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 2ef17d1476ab26bce89764e2f16833d7f52acc38; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 907c630e58af9e86e215f3951c7b287bd86d0f15; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 6301fe4f209165334d251a1c6da8ae47f93cb32c; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 4a2bf707270f897ab8077baee8ed5842a5321686; 6.3 | 30cad87978057516c93467516bc481a3eacfd66a, 2ef17d1476ab26bce89764e2f16833d7f52acc38, 907c630e58af9e86e215f3951c7b287bd86d0f15, 6301fe4f209165334d251a1c6da8ae47f93cb32c, 4a2bf707270f897ab8077baee8ed5842a5321686 |
| Linux | Linux Kernel | 6.3 up to, but not including, 6.6.103; 6.7 up to, but not including, 6.12.43; 6.13 up to, but not including, 6.15.11; 6.16 up to, but not including, 6.16.2 | 6.6.103, 6.12.43, 6.15.11, 6.16.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/2ef17d1476ab26bce89764e2f16833d7f52acc38
- git.kernel.org/stable/c/30cad87978057516c93467516bc481a3eacfd66a
- git.kernel.org/stable/c/4a2bf707270f897ab8077baee8ed5842a5321686
- git.kernel.org/stable/c/6301fe4f209165334d251a1c6da8ae47f93cb32c
- git.kernel.org/stable/c/907c630e58af9e86e215f3951c7b287bd86d0f15
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 9.1 Critical severity
Spotted an error? Tell us.