Vulnerability in drm/virtio package: NULL pointer dereference in virtio_gpu_conn_get_modes
Summary
GSD-2022-1003157: drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes. Affects Kernel versions < c51d00472fa54b9b05c17789ed665c17adf3a25d. 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 drm/virtio package is a component of the Linux Kernel that provides support for the VirtIO GPU driver. This driver enables virtualized graphics acceleration for virtual machines running on the VirtIO framework. It allows guest operating systems to utilize the host's GPU resources efficiently. However, a vulnerability has been discovered in the virtio_gpu_conn_get_modes function, which can lead to a NULL pointer dereference.
Vulnerability Detail
The vulnerability in the virtio_gpu_conn_get_modes function of the drm/virtio package allows an attacker to trigger a NULL pointer dereference. This can occur when the function is called with a NULL pointer as an argument, leading to a crash or potential privilege escalation. The impact of this vulnerability depends on the context in which the function is called and the privileges of the attacker. If successfully exploited, it could result in a denial of service or the execution of arbitrary code with kernel-level privileges.
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 Linux Kernel to the fixed version to mitigate the risk.
Conclusion
In conclusion, the vulnerability in the drm/virtio package can lead to a NULL pointer dereference, potentially resulting in a denial of service or the execution of arbitrary code with kernel-level privileges. It is crucial to update the Linux Kernel to version v5.17.14 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the context and privileges of the attacker. It could lead to a denial of service or the execution of arbitrary code with kernel-level privileges.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk.
You can find more information about the fix in the Linux Kernel repository. The fix is included in commit c51d00472fa54b9b05c17789ed665c17adf3a25d.
The vulnerability was discovered by an automated process and reported in the Open Source Vulnerability format. The actual impact and attack plausibility have not yet been proven.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
