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-1001856: drm/amd/display: Add affected crtcs to atomic state for dsc mst unplug. Affects Kernel versions >= 44be939ff7ac5858f0dbd8a2a4af1fe198e14db1, < 0f47edc22c2b7e4c1903d74c3992f09db9453d11. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The drm/amd/display package is a component of the Linux Kernel that handles display functionality for AMD graphics cards. It provides the necessary drivers and interfaces for managing and controlling the display output. This vulnerability specifically affects the handling of Display Stream Compression (DSC) Multi-Stream Transport (MST) unplug events. DSC is a feature that allows for the compression of display data, reducing bandwidth requirements. MST enables the connection of multiple displays through a single DisplayPort connection. The vulnerability arises from a missing step in the atomic state update process when handling DSC MST unplug events.

Vulnerability Detail

The vulnerability occurs due to a missing step in the atomic state update process when handling DSC MST unplug events in the drm/amd/display package. This omission can lead to inconsistent or incorrect state information, potentially resulting in display issues or system instability. An attacker could potentially exploit this vulnerability to manipulate the display output or trigger a denial-of-service condition. The vulnerability was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.15.33.

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 specific workaround has been provided for this vulnerability.

Conclusion

The vulnerability in the drm/amd/display package, specifically related to the handling of DSC MST unplug events, can lead to display issues or system instability. It is crucial to update the Linux Kernel to version v5.15.33 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in display issues or system instability, potentially allowing an attacker to manipulate the display output or trigger a denial-of-service condition.

You can use the Vulert Playground (https://vulert.com/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.

There is currently no known exploit for this vulnerability. However, it is still recommended to update to the fixed version of the Linux Kernel to mitigate any potential risks.

This vulnerability requires local access to the affected system. It cannot be exploited remotely.

Updating to the fixed version of the Linux Kernel is the primary recommended security measure to protect against this vulnerability. Additionally, it is always advisable to follow best practices for system security, such as regularly applying security updates and patches.

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