Vulnerability in Kernel: nvmet: fix freeing unallocated p2pmem
Summary
GSD-2021-1000766: nvmet: fix freeing unallocated p2pmem. Affects Kernel versions >= c6e3f13398123a008cd2ee28f93510b113a32791, < c440cd080761b18a52cac20f2a42e5da1e3995af. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a crucial component of the Linux operating system that provides essential services and functions to enable the system's operation. It acts as a bridge between the hardware and software layers, managing resources, facilitating communication, and ensuring security. The nvmet module within the Kernel is responsible for handling NVMe over Fabrics (NVMe-oF) storage devices. NVMe-oF allows remote access to NVMe storage devices over a network, providing high-performance storage capabilities. However, a vulnerability has been identified in the nvmet module that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in the nvmet module involves freeing unallocated p2pmem. This issue could be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with kernel privileges. The vulnerability was introduced in version v5.8 of the Linux Kernel by commit c6e3f13398123a008cd2ee28f93510b113a32791 and is fixed in version v5.10.43 by commit c440cd080761b18a52cac20f2a42e5da1e3995af. 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
As a temporary workaround, users can disable the nvmet module if it is not required for their system. This can be done by blacklisting the module or preventing it from loading during system startup. However, this workaround should only be considered if the nvmet functionality is not essential for the system's operation.
Conclusion
In conclusion, a vulnerability has been identified in the nvmet module of the Kernel, which could potentially lead to security issues. It is recommended to update the Linux Kernel to version v5.10.43 or later to mitigate this vulnerability. Users can also consider disabling the nvmet module as a temporary workaround if it is not essential for their system. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The nvmet module is a component of the Linux Kernel that handles NVMe over Fabrics (NVMe-oF) storage devices. It enables remote access to NVMe storage devices over a network.
The impact of this vulnerability is not yet proven, but it could potentially lead to a denial-of-service (DoS) condition or allow an attacker to execute arbitrary code with kernel privileges.
This vulnerability was introduced in version v5.8 of the Linux Kernel by commit c6e3f13398123a008cd2ee28f93510b113a32791.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.43 or later. Instructions for obtaining and compiling the updated Kernel source code can be found in the official Git repository.
Yes, as a temporary workaround, users can disable the nvmet module if it is not required for their system. This can be achieved by blacklisting the module or preventing it from loading during system startup.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
