Memory Leak in drm/selftests/test-drm_dp_mst_helper

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001865: drm/selftests/test-drm_dp_mst_helper: Fix memory leak in sideband_msg_req_encode_decode. Affects Kernel versions >= 09234b88ef5598252d1cee37e4d7b26a48b6557f, < 0728ccb66468b7a59959f9f4fb518ff9c655485f. 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/selftests/test-drm_dp_mst_helper is a self-test module in the Linux Kernel that is responsible for testing the functionality of the DisplayPort Multi-Stream Transport (DP MST) helper. DP MST is a feature that allows multiple displays to be connected to a single DisplayPort output. The test-drm_dp_mst_helper module is used to verify the correct operation of the DP MST helper functions. However, a memory leak vulnerability has been discovered in the sideband_msg_req_encode_decode function of this module.

Vulnerability Detail

The sideband_msg_req_encode_decode function in drm/selftests/test-drm_dp_mst_helper is vulnerable to a memory leak. This vulnerability can be exploited by an attacker to exhaust system memory resources, leading to a denial of service condition. The function fails to release allocated memory when an error occurs during the encoding or decoding of sideband messages. As a result, memory resources are not properly freed, causing a gradual depletion of available memory over time. This can eventually lead to system instability or crashes.

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 recommended to apply the fix by updating the Linux Kernel to a version that includes the patch.

Conclusion

The memory leak vulnerability in the sideband_msg_req_encode_decode function of drm/selftests/test-drm_dp_mst_helper can lead to a gradual depletion of system memory resources, potentially causing system instability or crashes. It is recommended to update the Linux Kernel to version v5.15.33 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to a gradual depletion of system memory resources, potentially causing system instability or crashes.

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 to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities are present.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to prevent potential attacks.

No, this vulnerability requires local access to the system in order to exploit it.

The only mitigation for this vulnerability is to update the Linux Kernel to a version that includes the fix.

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