Vulnerability in drm/mediatek Package: Add vblank register/unregister callback functions

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002796: drm/mediatek: Add vblank register/unregister callback functions. Affects Kernel versions >= 9b0704988b151824a51133dc4c921f4273c5d839, < 3a4027b5971fe2a94e32754f007d9d3c12c68ad1. 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 Penetration testing for web, API and mobile 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/mediatek package is a component of the Linux Kernel that provides support for display controllers found in MediaTek SoCs. It enables the management of display-related operations, including modesetting, framebuffer management, and synchronization. The package is responsible for handling the display output on devices that utilize MediaTek chipsets. However, a vulnerability has been identified in the package that could potentially be exploited by attackers.

Vulnerability Detail

The vulnerability in the drm/mediatek package involves the lack of vblank register/unregister callback functions. This issue was introduced in version v5.12 of the Linux Kernel and fixed in version v5.18.3. The absence of these callback functions could lead to various security risks, although the exact impact and attack plausibility have not been proven. It is important to note that this vulnerability has been identified through an automated process and further investigation is required to fully assess its potential ramifications.

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 this vulnerability has been fixed in the latest version of the Linux Kernel, applying the update is the recommended solution. However, if updating is not immediately feasible, it is advisable to follow security best practices such as restricting access to vulnerable systems, implementing network segmentation, and monitoring for any suspicious activity.

Conclusion

In conclusion, a vulnerability has been discovered in the drm/mediatek package of the Linux Kernel. This vulnerability involves the absence of vblank register/unregister callback functions, which could potentially lead to security risks. It is recommended to update the Linux Kernel to version v5.18.3 or later to address this vulnerability. If immediate updating is not possible, implementing security best practices and monitoring for any suspicious activity can help mitigate potential risks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The exact impact of this vulnerability is currently unknown. While the absence of vblank register/unregister callback functions could potentially lead to security risks, further investigation is required to determine the specific consequences.

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 provide real-time monitoring and alerts for open-source vulnerabilities, including this one.

While updating the Linux Kernel to the latest version is the recommended solution, if immediate updating is not possible, you can follow security best practices such as restricting access to vulnerable systems, implementing network segmentation, and monitoring for any suspicious activity.

At the time of this report, no known exploits for this vulnerability have been identified. However, it is crucial to apply the necessary updates and security measures to mitigate potential risks.

For more information about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

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