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-1000659: drm/amd/display: watermark latencies is not enough on DCN31. Affects Kernel versions < f4b4b70ba1e7069fa4c30ac75d698e7e6ea933c0. 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 is responsible for managing various aspects of the display pipeline, including setting up watermarks to ensure optimal display quality. Watermarks are used to control the amount of data that can be transferred between different display components, such as the GPU and the display controller. Insufficient watermark latencies on DCN31, a specific display controller, can lead to potential security vulnerabilities.

Vulnerability Detail

The vulnerability in the drm/amd/display package arises from the inadequate implementation of watermark latencies on DCN31. Watermark latencies are crucial for maintaining synchronization and preventing data corruption during data transfers. Insufficient latencies can result in timing-related issues, such as data overflows or underflows, which may lead to display artifacts, data corruption, or even potential security exploits. Attackers could potentially exploit these vulnerabilities to gain unauthorized access or execute arbitrary code on affected systems.

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

There is no known workaround for this vulnerability. It is essential to apply the provided fix by updating the Linux Kernel to the recommended version.

Conclusion

In conclusion, the vulnerability in the drm/amd/display package, specifically related to insufficient watermark latencies on DCN31, can lead to display issues, data corruption, and potential security exploits. It is crucial to update the Linux Kernel to version v5.16.8 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 result in display artifacts, data corruption, and potential security exploits. Attackers may exploit this vulnerability to gain unauthorized access or execute arbitrary code on affected systems.

Systems running the Linux Kernel with the drm/amd/display package, specifically on DCN31 display controllers, are affected by this vulnerability.

No, there is no known workaround for this vulnerability. It is crucial to apply the provided fix by updating the Linux Kernel to the recommended version.

Users can update the Linux Kernel by obtaining the latest version from the official Linux Kernel repository or through their respective Linux distribution's package management system.

For more information about this vulnerability, refer to the provided references link in the vulnerability details section.

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