Null Pointer Dereference in drm/v3d Package
Summary
GSD-2022-1002771: drm/v3d: Fix null pointer dereference of pointer perfmon. Affects Kernel versions >= 26a4dc29b74a137f45665089f6d3d633fcc9b662, < 3b72deb784a7d4ae8519a5c584cd87c4b57aa6c8. 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/v3d package is a component of the Linux Kernel that provides support for the Broadcom V3D graphics driver. This driver is used for hardware acceleration on certain Broadcom GPUs. The package allows applications to communicate with the GPU and utilize its capabilities for rendering graphics. However, a vulnerability has been discovered in the package that can lead to a null pointer dereference.
Vulnerability Detail
The null pointer dereference vulnerability in the drm/v3d package occurs when the 'perfmon' pointer is dereferenced without proper validation. This can result in a crash or potentially allow an attacker to execute arbitrary code in the context of the affected process. The vulnerability was introduced in version v5.15 of the Linux Kernel and has been fixed in version v5.18.3.
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 recommended to apply the fix mentioned above as soon as possible.
Conclusion
The null pointer dereference vulnerability in the drm/v3d package can lead to crashes or potential code execution. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a crash or allow an attacker to execute arbitrary code in the context of the affected process.
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 and the playground will analyze it for any known vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The vulnerability requires an attacker to have local access to the affected system. It cannot be exploited remotely over a network connection.
This vulnerability specifically affects the drm/v3d package in the Linux Kernel. There are no known dependencies or other packages directly impacted.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
