Use After Free Vulnerability in drbd
Summary
GSD-2022-1001355: drbd: Fix five use after free bugs in get_initial_state. Affects Kernel versions >= a29728463b254ce81ecefdf20c1a02e01d9361da, < de63e74da2333b4068bb79983e632db730fea97e. 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 drbd package is a distributed replicated block device driver for Linux. It allows multiple servers to share the same storage device, providing high availability and data redundancy. The vulnerability in question is related to the get_initial_state function within the drbd code.
Vulnerability Detail
The vulnerability is characterized by five instances of use after free bugs in the get_initial_state function of the drbd package. These bugs can potentially be exploited by an attacker to execute arbitrary code or cause a denial of service. The vulnerability was introduced in version 4.5 of the Linux Kernel and has been fixed in version 5.16.20.
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 apply the fix mentioned above to ensure the security of the system.
Conclusion
The use after free vulnerability in the drbd package's get_initial_state function can lead to arbitrary code execution or denial of service. It is crucial to update the Linux Kernel to version 5.16.20 or later to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can be exploited by an attacker to execute arbitrary code or cause a denial of service.
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 and the tool will provide real-time alerts for any open-source vulnerabilities.
No, there is no known workaround for this vulnerability. It is crucial to apply the fix mentioned above.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network.
There is no information available regarding active exploitation of this vulnerability in the wild at the moment.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
