Vulnerability in drm/amd/display Package: Insufficient Watermark Latencies on DCN31

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000576: drm/amd/display: watermark latencies is not enough on DCN31. Affects Kernel versions < 7ff0ed88e4eb6bd7ccd7cf422ab855032ed0528c. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The drm/amd/display package is a component of the Linux Kernel ecosystem. It is responsible for managing display functionality on AMD graphics cards. The package includes various features and modules that handle tasks such as display configuration, mode setting, and video playback. One critical aspect of display management is the implementation of watermarks, which ensure the correct placement and timing of display content. However, on DCN31 (Display Core Next 31) architecture, the watermark latencies are insufficient, leading to potential vulnerabilities.

Vulnerability Detail

The vulnerability in the drm/amd/display package arises from inadequate watermark latencies on DCN31 architecture. Watermark latencies play a crucial role in maintaining the integrity and synchronization of display content. Insufficient latencies can result in visual artifacts, tearing, or incorrect rendering of content. Attackers may exploit this vulnerability to manipulate or disrupt the display output, potentially leading to information disclosure or denial of service attacks. The vulnerability has been identified and fixed in Linux Kernel version v5.15.22 through commit 7ff0ed88e4eb6bd7ccd7cf422ab855032ed0528c.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.22 or later. This can be done by pulling the latest changes from the official Linux Kernel repository using the following command:

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Once the repository is cloned, navigate to the cloned directory and checkout the desired version:

$ cd linux $ git checkout v5.15.22

Finally, rebuild and reinstall the kernel to apply the fix.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can disable the affected display functionality on DCN31 architecture. This can be achieved by modifying the kernel configuration or using kernel boot parameters to exclude the affected module. However, it is important to note that this workaround may result in limited or degraded display capabilities.

Conclusion

In conclusion, the vulnerability in the drm/amd/display package arises from insufficient watermark latencies on DCN31 architecture. This can result in visual artifacts, tearing, or incorrect rendering of display content. It is crucial to update the Linux Kernel to version v5.15.22 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to visual artifacts, tearing, or incorrect rendering of display content. It may also be exploited by attackers to manipulate or disrupt the display output, potentially resulting in information disclosure or denial of service attacks.

The vulnerability affects versions of the Linux Kernel prior to v5.15.22.

This vulnerability was discovered through ongoing security research and analysis of the Linux Kernel codebase.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is advisable to apply the recommended fix to mitigate any potential risks.

Yes, you can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.22 or later. This can be done by pulling the latest changes from the official Linux Kernel repository using the following command:

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Once the repository is cloned, navigate to the cloned directory and checkout the desired version:

$ cd linux $ git checkout v5.15.22

Finally, rebuild and reinstall the kernel to apply the fix.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.