CVE-2023-53789
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-09
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's AMD IOMMU (Input-Output Memory Management Unit) driver. If the IOMMU domain for a device group is not properly set up, the kernel's page fault handler assumes the domain is always set up and attempts to access it, leading to a NULL pointer dereference. This causes a kernel crash or 'oops' due to an invalid memory access when handling IOMMU page faults.
How can this vulnerability impact me? :
The vulnerability can cause the Linux kernel to crash or become unstable due to a NULL pointer dereference when an IOMMU page fault occurs and the domain is not properly set up. This can lead to system instability, potential denial of service, and interruption of device operations relying on the IOMMU.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel NULL pointer dereference errors related to IOMMU page faults. Specifically, look for log entries similar to the sample provided, which include messages like 'BUG: kernel NULL pointer dereference' and references to 'report_iommu_fault'. Commands such as 'dmesg | grep -i iommu' or 'journalctl -k | grep -i iommu' can help identify these errors in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves ensuring that the IOMMU domain for the device group is properly set up to prevent page faults that lead to NULL pointer dereferences. Applying the relevant Linux kernel updates or patches that improve page fault error reporting and check domain setup is recommended. Until patched, monitoring logs for the described errors and avoiding configurations that might cause improper IOMMU domain setup can help reduce risk.