Vulnerability in Linux Kernel: hv: vmbus: Deactivate sysctl_record_panic_msg by default in isolated guests
Summary
GSD-2022-1001654: Drivers: hv: vmbus: Deactivate sysctl_record_panic_msg by default in isolated guests. Affects Kernel versions < 1b576e81d31b56b248316b8ff816b1cc5c4407c7. 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 the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. It is a crucial part of the Linux ecosystem and widely used in various devices and systems. The vmbus driver in the Kernel is responsible for communication between the host and guest operating systems in a virtualized environment. It allows for efficient data transfer and device enumeration. However, a vulnerability has been discovered in the vmbus driver that affects isolated guests.
Vulnerability Detail
The vulnerability in the vmbus driver of the Linux Kernel allows an attacker to exploit a sysctl_record_panic_msg feature that is enabled by default in isolated guests. This feature records panic messages in the hypervisor log, which can potentially expose sensitive information or aid in further attacks. By deactivating this feature by default, the impact of such attacks can be mitigated. The vulnerability has not been proven to be exploitable yet, but it is recommended to address it as a precautionary measure.
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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the vmbus driver of the Linux Kernel, which enables the sysctl_record_panic_msg feature by default in isolated guests, has been identified. While the impact and exploitability of this vulnerability are not proven, it is recommended to update the Linux Kernel to version v5.15.35 or later to deactivate this feature and reduce the potential attack surface. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to expose sensitive information or aid in further attacks by recording panic messages in the hypervisor log.
This vulnerability is present in the Linux Kernel versions prior to v5.15.35. Updating to the latest version will mitigate the risk.
No, only isolated guests are affected by this vulnerability. Guests running in a non-isolated environment are not impacted.
There is no known exploit for this vulnerability at the moment. However, it is recommended to address it as a precautionary measure.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.