CVE-2025-38157
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 3.0 (inc) to 5.4.295 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.239 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.186 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.142 (exc) |
| linux | linux_kernel | From 6.2 (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) |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's ath9k_htc wireless driver. A malicious USB device can send a specific event (WMI_SWBA_EVENTID) before beaconing is enabled, causing a division by zero error in the driver. This leads to either a system crash or an out-of-bounds memory read. The issue is fixed by aborting the event handling if beaconing is not enabled.
How can this vulnerability impact me? :
The vulnerability can cause the affected system to crash or behave unpredictably due to out-of-bounds memory reads. This can lead to denial of service or potential instability in systems using the ath9k_htc wireless driver when exposed to a malicious USB device.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure your Linux kernel is updated to a version where the ath9k_htc driver has the fix that aborts software beacon handling if disabled. Avoid connecting untrusted USB devices that could exploit this vulnerability until the patch is applied.