CVE-2023-54174
NULL Pointer Dereference in Linux vfio Causes Kernel Crash
Publication date: 2025-12-30
Last updated on: 2025-12-30
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 is a NULL pointer dereference in the Linux kernel's vfio component. It occurs because the group->iommufd pointer is not initialized before being used in the iommufd_ctx_put() function, which can cause the kernel to crash or behave unexpectedly.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be done by monitoring the system logs for kernel NULL pointer dereference errors related to iommufd. Specifically, look for messages similar to: '[timestamp] BUG: kernel NULL pointer dereference, address: 0000000000000000' and call traces involving 'iommufd_ctx_put' and 'vfio_group_fops_unl_ioctl'. You can use the command 'dmesg | grep -i iommufd' or 'journalctl -k | grep -i iommufd' to find such logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the vfio NULL pointer dereference caused by uninitialized group->iommufd is fixed. Until then, avoid using features or modules that trigger the vulnerable code path, such as vfio with iommufd. Monitoring for kernel crashes and applying kernel patches as soon as they are available is recommended.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can cause a kernel crash (NULL pointer dereference), potentially leading to a denial of service or system instability.