Vulnerability in Linux Kernel: hv: vmbus
Summary
GSD-2022-1000973: Drivers: hv: vmbus: Deactivate sysctl_record_panic_msg by default in isolated guests. Affects Kernel versions < 6230bc50d6d21cae4c084766623d0a6d17958721. 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 Linux Kernel is a widely used open-source operating system that serves as the foundation for various Linux distributions. It provides essential functionality and device drivers for hardware components. One of the drivers included in the Kernel is the 'hv: vmbus' driver, which facilitates communication between the host and virtual machines running on Microsoft Hyper-V. This driver is responsible for handling messages and data transfers between the host and guest systems. However, a vulnerability has been discovered in the 'hv: vmbus' driver that affects isolated guests.
Vulnerability Detail
The vulnerability in the 'hv: vmbus' driver allows an attacker with access to an isolated guest system to potentially exploit the 'sysctl_record_panic_msg' feature. By default, this feature is active in isolated guests, which means that the guest system records panic messages in the hypervisor's log. However, if an attacker can trigger a panic condition in the guest system, they may be able to inject malicious data into the panic message, potentially leading to further exploitation or denial of service attacks. This vulnerability has been addressed in Linux Kernel version v5.17.4 by deactivating the 'sysctl_record_panic_msg' feature by default in isolated guests.
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 workaround, if updating the Kernel is not immediately feasible, you can manually deactivate the 'sysctl_record_panic_msg' feature in isolated guests. This can be done by modifying the relevant sysctl configuration file or using the 'sysctl' command-line tool. However, it is strongly recommended to apply the official fix by updating the Kernel as soon as possible.
Conclusion
The 'hv: vmbus' driver in the Linux Kernel is vulnerable to potential exploitation of the 'sysctl_record_panic_msg' feature in isolated guest systems. This vulnerability has been addressed in Linux Kernel version v5.17.4 by deactivating the feature by default. It is recommended to update the Kernel to the latest version to mitigate the risk. If immediate update is not feasible, manually deactivating the feature can serve as a temporary workaround. For further support and assistance, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability allows an attacker with access to an isolated guest system to potentially exploit the 'sysctl_record_panic_msg' feature, leading to possible further exploitation or denial of service attacks.
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 to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
No, this vulnerability requires an attacker to have access to an isolated guest system in order to potentially exploit the 'sysctl_record_panic_msg' feature.
There are no known instances of this vulnerability being exploited in the wild at the time of this report. However, it is still important to apply the necessary fixes to mitigate the risk.
For further support and assistance with vulnerability remediation, you can contact info@devnack.com. They can provide guidance and help ensure your system is secure.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
