Use-after-free vulnerability in lpfc_unreg_rpi() routine in Kernel
Summary
GSD-2021-1002334: scsi: lpfc: Fix use-after-free in lpfc_unreg_rpi() routine. Affects Kernel versions < dbebf865b3239595c1d4dba063b122862583b52a. 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 Kernel is a critical component of the Linux operating system that manages the communication between hardware and software. It provides essential services and functions for the proper functioning of the system. The lpfc driver in the Kernel is responsible for managing SCSI devices. It allows the system to communicate with storage devices such as hard drives and solid-state drives. However, a use-after-free vulnerability has been discovered in the lpfc_unreg_rpi() routine of the lpfc driver.
Vulnerability Detail
The use-after-free vulnerability in the lpfc_unreg_rpi() routine occurs when a SCSI device is unregistered. This vulnerability could be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. By manipulating the system's memory after it has been freed, an attacker can potentially gain control over the system or crash it. This vulnerability poses a significant risk to the security and stability of the affected systems.
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
There is no known workaround for this vulnerability. It is essential to update the Kernel to the fixed version as soon as possible to protect the system from potential exploitation.
Conclusion
The use-after-free vulnerability in the lpfc_unreg_rpi() routine of the Kernel's lpfc driver poses a significant risk to the security and stability of affected systems. It is crucial to update the Kernel to version v5.15.5 or later, which includes the fix for this vulnerability. Failure to patch the Kernel could result in potential exploitation by attackers. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition on the affected system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes the manifest file like package-lock.json to identify vulnerabilities in the software.
At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to update the Kernel to the fixed version to mitigate the risk.
Yes, this vulnerability can be remotely exploited if the affected system is accessible over a network. It is recommended to update the Kernel to the fixed version to prevent potential remote exploitation.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide assistance and guidance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.