CVE-2025-38595
BaseFortify
Publication date: 2025-08-19
Last updated on: 2025-11-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| 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) issue in the Linux kernel's xen subsystem, specifically in the dmabuf_exp_from_pages() function. The problem occurs because after inserting a file reference into the descriptor table, another thread could close it, leading to a race condition. If the kernel accesses objects that are destroyed upon closing the file descriptor (such as the struct file or related resources), it results in a use-after-free error. The fix involves reserving the descriptor before any other operations and only installing the file descriptor after all setup is complete, preventing access to freed objects.
How can this vulnerability impact me? :
This use-after-free vulnerability can lead to undefined behavior in the kernel, including potential crashes, memory corruption, or escalation of privileges. Exploiting this flaw could allow an attacker to execute arbitrary code within the kernel context or cause denial of service by crashing the system.