Vulnerability in drm/virtio package: NULL pointer dereference in virtio_gpu_conn_get_modes
Summary
GSD-2022-1002834: drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes. Affects Kernel versions < 0f8bc147a963686b7351aa35d1701124ffacac08. 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 ecosystem. It provides support for the VirtIO GPU driver, which allows virtual machines to utilize the host's GPU resources. The virtio_gpu_conn_get_modes function is responsible for retrieving the available display modes for a VirtIO GPU connection. However, a vulnerability exists in this function that can lead to a NULL pointer dereference.
Vulnerability Detail
The vulnerability in the virtio_gpu_conn_get_modes function arises from a failure to handle NULL pointers correctly. When called with a NULL pointer as the 'conn' parameter, the function does not perform proper validation, leading to a dereference of the NULL pointer. An attacker could exploit this vulnerability by providing a specially crafted input that triggers the NULL pointer dereference, potentially resulting in a system crash or other unexpected behavior. The impact and attack plausibility of this vulnerability have not been proven yet.
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
No workaround has been provided for this vulnerability.
Conclusion
In conclusion, the vulnerability in the drm/virtio package's virtio_gpu_conn_get_modes function can lead to a NULL pointer dereference. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.18.3 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown. It could potentially lead to a system crash or other unexpected behavior.
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 to the playground, and it will alert you if the vulnerability is present.
There is currently no known exploit for this vulnerability. However, it is still important to update to the latest version of the Linux Kernel to ensure the security of your system.
The recommended mitigation is to update the Linux Kernel to version v5.18.3 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2022-1002834 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002834.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
