Null Pointer Dereference in drm/rockchip: vop_bind()
Summary
GSD-2022-1003130: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind(). Affects Kernel versions >= 2048e3286f347db5667708e47448176b5329e8d8, < 769c53bb6116d0eaec0f1fe4ec4b27a74465cad1. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The drm/rockchip package is a component of the Linux Kernel that provides support for Rockchip display controllers. These display controllers are commonly found in Rockchip SoCs (System on Chips) used in various devices such as tablets, smartphones, and embedded systems. The vop_bind() function within the package is responsible for binding display pipelines to the display controller. However, a vulnerability has been discovered in this function that could lead to a null pointer dereference.
Vulnerability Detail
The vulnerability in the vop_bind() function of drm/rockchip can result in a null pointer dereference. This occurs when the function fails to properly handle a null pointer, leading to a crash or potential privilege escalation. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial of service. The vulnerability was introduced in version v3.19 of the Linux Kernel and has been fixed in version v5.17.14.
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 update the Linux Kernel to the fixed version.
Conclusion
The null pointer dereference vulnerability in the vop_bind() function of drm/rockchip can have serious security implications. It is crucial to update the Linux Kernel to version v5.17.14 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial of service.
You can use the Vulert Playground (https://vulert.com/scanner) without any signup to check if your system is affected.
Yes, the vulnerability has been fixed in version v5.17.14 of the Linux Kernel.
There is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
You can refer to the vulnerability details in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003130.json) for more information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
