CVE-2025-38594
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 | 6.16 |
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) error in the Linux kernel's iommu/vt-d component. It occurs when the system improperly removes a device from its IOMMU's IOPF queue while there are still pending IOPFs (Input/Output Page Faults). This incorrect removal can trigger a use-after-free condition, potentially leading to a kernel panic and system crash.
How can this vulnerability impact me? :
The vulnerability can cause a kernel panic, which leads to a system crash. This can result in denial of service, affecting system stability and availability. In environments relying on the Linux kernel's iommu/vt-d functionality, this could disrupt normal operations and potentially cause data loss or downtime.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the kernel logs for specific error messages indicating a use-after-free condition related to IOPF in the iommu/vt-d subsystem. Look for kernel panic traces containing messages such as 'refcount_t: underflow; use-after-free' and warnings from 'lib/refcount.c'. Commands like 'dmesg | grep -i "use-after-free"' or 'journalctl -k | grep -i "refcount_t: underflow"' can help identify if the system has encountered this issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the fix where the iopf_for_domain_remove() call is moved after intel_pasid_tear_down_entry(), preventing the use-after-free error. Until an update is applied, monitoring for kernel panics and avoiding workloads that trigger IOPF detachments may reduce risk. There are no specific configuration changes or workarounds detailed.