Use-after-free read vulnerability in drm_getunique() in Kernel

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000892: drm: Fix use-after-free read in drm_getunique(). Affects Kernel versions < b246b4c70c1250e7814f409b243000f9c0bf79a3. 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 Kernel is a critical component of the Linux operating system that manages communication between hardware and software. It provides essential functionalities for device drivers, memory management, and process scheduling. The drm_getunique() function is part of the Direct Rendering Manager (DRM) subsystem in the Kernel, which handles graphics and display-related operations. This vulnerability specifically affects the drm_getunique() function.

Vulnerability Detail

The use-after-free read vulnerability in drm_getunique() allows an attacker to read data from a freed memory location. This can lead to information disclosure or potentially be exploited to execute arbitrary code. The vulnerability originates from improper handling of memory deallocation in the drm_getunique() function. By manipulating certain parameters, an attacker can trigger the use-after-free condition and access sensitive information or execute malicious code.

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

  1. Download the patch file from the provided source link.
  2. Navigate to the Kernel source code directory.
  3. Apply the patch using the 'git apply' command.

Please note that applying patches manually requires knowledge of the Linux Kernel build process and may not be suitable for all users.

Conclusion

The use-after-free read vulnerability in drm_getunique() poses a risk of information disclosure and arbitrary code execution. It is crucial to update the Linux Kernel to version v5.4.126 or later, which includes the necessary fix. Alternatively, users can manually apply the provided patch. For further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free read vulnerability in drm_getunique() can potentially lead to information disclosure or arbitrary code execution. Attackers may be able to access sensitive data or compromise the system's security.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended patch or update to protect your system from potential exploitation.

While updating the Kernel is the recommended solution, you can apply the provided patch manually as a temporary mitigation. However, keep in mind that manual patching requires expertise and may not be suitable for all users.

You can find more information about this vulnerability, including its technical details and the fix, in the provided source link: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000892.json

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