CVE-2025-71075
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 2.6.19 |
| linux | linux_kernel | From 5.11 (inc) to 5.15.198 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.160 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.120 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.64 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.3 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 2.6.19.1 (inc) to 5.10.248 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in the Linux kernel's scsi aic94xx driver. Specifically, the asd_pci_remove() function does not properly synchronize with pending tasklets before freeing the asd_ha structure during device removal. This can cause a race condition where the system may access memory that has already been freed, potentially leading to instability or crashes. The fix involves adding tasklet_kill() to ensure all scheduled tasklets complete before the structure is freed.
How can this vulnerability impact me? :
This vulnerability can lead to system instability, crashes, or unpredictable behavior when a device using the affected driver is removed (such as during hot-unplug or module unload). Exploiting the use-after-free condition could potentially allow an attacker to cause denial of service or execute arbitrary code, depending on the context and system configuration.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the use-after-free issue in the aic94xx driver. The fix involves adding tasklet_kill() before freeing the asd_ha structure to ensure proper synchronization during device removal. Avoid hot-unplugging devices or unloading the module until the kernel is updated.