CVE-2025-38056
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 (UAF) bug in the Linux kernel's ASoC SOF Intel HDA driver. Specifically, when the module is reloaded, a global variable points to memory that has already been freed, leading to a use-after-free read. This happens because a string allocated with devm_kasprintf() is stored in a global variable and freed when the module unloads, but the variable is not updated properly before reloading. The fix involves copying the match array with devm_kmemdup_array() before modifying it to avoid referencing freed memory.
How can this vulnerability impact me? :
This use-after-free vulnerability can lead to kernel crashes or undefined behavior when the affected module is reloaded, potentially causing system instability or denial of service. In some cases, such vulnerabilities might be exploitable to execute arbitrary code or escalate privileges, but the provided information does not specify such exploitation.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix is applied. The fix involves copying the match array with devm_kmemdup_array() before modification to prevent use-after-free. Avoid unloading and reloading the affected snd_sof_intel_hda_generic module until the patch is applied.