Vulnerability in drm/virtio package: NULL pointer dereference in virtio_gpu_array_put_free()
Summary
GSD-2022-1001637: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free(). Affects Kernel versions >= 377f8331d0565e6f71ba081c894029a92d0c7e77, < ac92b474eeeed75b8660374ba1d129a121c09da8. 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 device. VirtIO is a standard interface for virtualized environments, allowing guest operating systems to communicate with virtual devices. The VirtIO GPU device is responsible for rendering graphics and providing display capabilities to virtual machines. This vulnerability affects the package's implementation of the virtio_gpu_array_put_free() function.
Vulnerability Detail
The vulnerability arises from a NULL pointer dereference in the virtio_gpu_array_put_free() function of the drm/virtio package. When the function is called with a NULL value for the 'objs' parameter, it fails to handle this case properly, leading to a potential crash or other undefined behavior. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel 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
As a workaround, users can avoid triggering the vulnerable code path by ensuring that the 'objs' parameter passed to virtio_gpu_array_put_free() is always a valid pointer. This can be achieved by performing proper input validation and error handling in the calling code.
Conclusion
In conclusion, the drm/virtio package in the Linux Kernel is vulnerable to a NULL pointer dereference in the virtio_gpu_array_put_free() function. This vulnerability can potentially lead to system crashes or arbitrary code execution. It is crucial to update the kernel to the latest version and apply the necessary patch to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially allow an attacker to crash the system or execute arbitrary code with kernel privileges.
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 alerts for open-source vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate potential risks.
The recommended mitigation is to update the Linux Kernel to the latest version that includes the fix for this vulnerability. Additionally, ensuring proper input validation and error handling in the calling code can help prevent triggering the vulnerable code path.
You can find more information about this vulnerability in the GSD database entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001637.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
