CVE-2025-39890
BaseFortify
Publication date: 2025-09-24
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.3 (inc) to 6.6.94 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.34 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.15.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's ath12k wireless driver. Specifically, in the function ath12k_service_ready_ext_event(), a memory allocation (svc_rdy_ext.mac_phy_caps) is not freed when an error occurs, causing the allocated memory to remain unreferenced and leaked. This issue was identified through kmemleak tracing and has been fixed by ensuring the memory is freed in the failure case.
How can this vulnerability impact me? :
The memory leak can cause the system to consume increasing amounts of memory over time, potentially leading to degraded performance or system instability, especially on devices using the affected ath12k wireless driver. This could result in crashes or reduced availability of wireless functionality.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for memory leaks related to the ath12k driver in the Linux kernel. Specifically, using kmemleak to identify unreferenced objects associated with ath12k_service_ready_ext_event. Commands such as `echo scan > /sys/kernel/debug/kmemleak` followed by `cat /sys/kernel/debug/kmemleak` can help detect memory leaks.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Linux kernel to a version where the ath12k_service_ready_ext_event memory leak has been fixed, as described in the patch that frees svc_rdy_ext.mac_phy_caps in the error case.