Kernel memory corruption via unallocated TID cleanup
Published Sep 11, 2025 · Updated Sep 11, 2025
Out-of-bounds access in the Linux ath12k Wi-Fi driver allows physically proximate attackers to corrupt kernel memory and crash the system. On a failed ath12k_dp_rx_peer_tid_setup call, the cleanup loop starts at an incremented but unallocated TID and passes rx_tid[17] to deletion, causing out-of-bounds reads and writes and an invalid free. An attacker within radio range can repeatedly send spoofed authentication or association frames to an ath12k access point before credentials are verified, exposing kernel memory, corrupting the heap, or causing an oops or panic.
Summary
What happened
Out-of-bounds access in the Linux ath12k Wi-Fi driver allows physically proximate attackers to corrupt kernel memory and crash the system. On a failed ath12k_dp_rx_peer_tid_setup call, the cleanup loop starts at an incremented but unallocated TID and passes rx_tid[17] to deletion, causing out-of-bounds reads and writes and an invalid free. An attacker within radio range can repeatedly send spoofed authentication or association frames to an ath12k access point before credentials are verified, exposing kernel memory, corrupting the heap, or causing an oops or panic.
The record
- CVE
- CVE-2025-39750
- Published
- Sep 11, 2025
- Updated
- Sep 11, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2025CVE publishedPublication date reported by the CVE source.
- Sep 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ef17d1476ab26bce89764e2f16833d7f52acc38
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <30cad87978057516c93467516bc481a3eacfd66a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4a2bf707270f897ab8077baee8ed5842a5321686
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6301fe4f209165334d251a1c6da8ae47f93cb32c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <907c630e58af9e86e215f3951c7b287bd86d0f15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo