Use after free vulnerability in hv vmbus driver
Summary
GSD-2021-1000379: Drivers: hv: vmbus: Use after free in __vmbus_open(). Affects Kernel versions >= 6f3d791f300618caf82a2be0c27456edd76d5164, < d5c7b42c9f56ca46b286daa537d181bd7f69214f. 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 hv vmbus driver is a component of the Linux Kernel that provides support for the Hyper-V virtualization platform. It allows communication between the host and guest operating systems running on a Hyper-V virtual machine. The driver is responsible for managing the virtual devices and facilitating data transfer between the host and guest. This vulnerability affects the hv vmbus driver and can potentially be exploited by an attacker to execute arbitrary code or escalate privileges on the affected system.
Vulnerability Detail
The vulnerability exists in the __vmbus_open() function of the hv vmbus driver. It is caused by a use-after-free bug, where a reference to a freed memory object is still being accessed. An attacker can trigger this vulnerability by sending specially crafted messages to the vmbus driver, leading to the use of the freed memory and potentially resulting in a system crash or arbitrary code execution. This vulnerability was introduced in version 4.14 of the Linux Kernel and has been fixed in version 5.10.37.
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 strongly advised to apply the official fix by updating the Linux Kernel.
Conclusion
The use after free vulnerability in the hv vmbus driver can potentially lead to arbitrary code execution or privilege escalation. It is crucial to update the Linux Kernel to version 5.10.37 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can be exploited by an attacker to execute arbitrary code or escalate privileges on the affected system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to malicious network traffic. It is recommended to apply the fix and ensure proper network security measures are in place.
The only effective mitigation for this vulnerability is to apply the official fix by updating the Linux Kernel to version 5.10.37 or later.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
