Vulnerability in drm/rockchip package: Possible Null Pointer Dereference in vop_bind()

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003917: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind(). Affects Kernel versions >= 2048e3286f347db5667708e47448176b5329e8d8, < 6ff986e057bf28e2f7690dad410768b2270f9453. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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-based devices such as tablets and embedded systems. The package includes various drivers and functions to enable proper display functionality on these devices. However, a vulnerability has been identified in the vop_bind() function of the package, which could lead to a null pointer dereference.

Vulnerability Detail

The vulnerability in the drm/rockchip package arises from a possible null pointer dereference in the vop_bind() function. This function is responsible for binding a display controller to a display pipeline. If a null pointer is encountered during the binding process, it can lead to a crash or other unexpected behavior. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) attack or execute arbitrary code. The vulnerability was introduced in version v3.19 of the Linux Kernel and has been fixed in version v4.19.247.

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 apply the patch manually to their existing kernel version. Here is an example of how to apply the patch:

  1. Download the patch file from the Linux Kernel repository.
  2. Navigate to the kernel source directory.
  3. Apply the patch using the patch command: patch -p1 < path/to/patch.file
  4. Recompile and reinstall the kernel.

Please note that applying patches manually can be complex and error-prone. It is recommended to update to the latest kernel version instead.

Conclusion

In conclusion, the drm/rockchip package in the Linux Kernel is vulnerable to a null pointer dereference in the vop_bind() function. This vulnerability can potentially lead to crashes, DoS attacks, or arbitrary code execution. It is crucial to update the Linux Kernel to version v4.19.247 or later to mitigate this vulnerability. Users can also apply the provided patch manually as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could lead to a crash or other unexpected behavior in systems utilizing the drm/rockchip package. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) attack or execute arbitrary code.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application or system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) 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 important to apply the necessary updates or patches to mitigate the risk.

The primary mitigation for this vulnerability is to update the Linux Kernel to version v4.19.247 or later. Additionally, users can apply the provided patch manually as a temporary workaround.

This vulnerability was discovered by an automated security analysis tool and reported to the Linux Kernel development team.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback