Vulnerability in nvme-pci: NULL pointer dereference in nvme_alloc_admin_tags
Summary
GSD-2022-1003070: nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags. Affects Kernel versions < 7a28556082d1fbcbc599baf1c24252dfc73efefc. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The nvme-pci package is a component of the Linux Kernel ecosystem. It provides support for NVMe (Non-Volatile Memory Express) devices connected via PCI. NVMe is a protocol designed for efficient communication between host systems and solid-state drives (SSDs). The nvme_alloc_admin_tags function within the package is responsible for allocating administrative tags for NVMe commands. These tags are used to identify and track commands sent to the NVMe device. However, a vulnerability has been discovered in this function that can lead to a NULL pointer dereference.
Vulnerability Detail
The vulnerability in nvme-pci arises from a NULL pointer dereference in the nvme_alloc_admin_tags function. When certain conditions are met, the function fails to properly handle a NULL pointer, leading to a crash or potential system instability. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges. The impact and attack plausibility of this vulnerability have not yet been proven.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
No workaround has been provided for this vulnerability.
Conclusion
The vulnerability in nvme-pci, which involves a NULL pointer dereference in the nvme_alloc_admin_tags function, can lead to system crashes, instability, or potential execution of arbitrary code with elevated privileges. It is crucial to update the Linux Kernel to version v5.17.14 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a system crash or instability to potential execution of arbitrary code with elevated privileges.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
Yes, a fix for this vulnerability is available in the Linux Kernel version v5.17.14. Updating the Kernel to this version or later will resolve the vulnerability.
The remote exploitability of this vulnerability has not been determined. However, it is recommended to apply the fix as soon as possible to mitigate any potential risks.
No workaround has been provided for this vulnerability. It is advised to update the Linux Kernel to the fixed version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.