Vulnerability in drm/amd/display Package: Add Affected CRTCs to Atomic State for DSC MST Unplug

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1002251: drm/amd/display: Add affected crtcs to atomic state for dsc mst unplug. Affects Kernel versions >= 992e51ff0e4b4237fa5c02cd85e383ef71411573, < 2eaa9d86e00713587635c7c9d9b4576d746ae101. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The drm/amd/display package is a component of the Linux Kernel, which is responsible for managing the display subsystem for AMD graphics cards. It provides the necessary functionality to control various aspects of the display, including resolution, refresh rate, and multiple display setups. This vulnerability specifically affects the handling of Display Stream Compression (DSC) Multi-Stream Transport (MST) unplug operations.

Vulnerability Detail

The vulnerability arises from a missing implementation in the drm/amd/display package, which fails to add the affected CRTCs (CRTC stands for Cathode Ray Tube Controller) to the atomic state during DSC MST unplug operations. This omission can lead to inconsistent display configurations and potential security risks. An attacker could potentially exploit this vulnerability to manipulate the display output or gain unauthorized access to sensitive information.

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

No workaround has been provided for this vulnerability.

Conclusion

The vulnerability in the drm/amd/display package, which fails to add affected CRTCs to the atomic state during DSC MST unplug operations, can be mitigated by updating the Linux Kernel to version v5.4.189 or later. This update ensures the necessary fix is applied, reducing the risk of inconsistent display configurations and potential security breaches. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The drm/amd/display package is a component of the Linux Kernel responsible for managing the display subsystem for AMD graphics cards.

DSC MST unplug refers to the operation of disconnecting a Display Stream Compression (DSC) Multi-Stream Transport (MST) setup.

CRTCs (Cathode Ray Tube Controllers) are responsible for controlling the display output of graphics cards.

This vulnerability can lead to inconsistent display configurations and potential security risks. An attacker could manipulate the display output or gain unauthorized access to sensitive information.

To fix this vulnerability, update the Linux Kernel to version v5.4.189 or later.

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