Refcount Leak in intel_dp_add_mst_connector() in Kernel

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004191: drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector(). Affects Kernel versions >= 091a4f91942a4396c67e5747f5cb38c6396d1fc5, < a91522b4279bebb098106a19b91f82b9c3213be9. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces with hardware devices. It manages system resources, including memory, processes, and input/output operations. The intel_dp_add_mst_connector() function is part of the Direct Rendering Manager (DRM) subsystem in the Kernel, specifically for the Intel integrated graphics driver (i915). This function is responsible for adding a multi-stream transport (MST) connector to the display pipeline. MST connectors enable the use of multiple displays through a single physical connection. However, a vulnerability has been discovered in this function that could lead to a refcount leak.

Vulnerability Detail

The vulnerability in intel_dp_add_mst_connector() can result in a refcount leak. A refcount leak occurs when the reference count of an object is not properly managed, leading to memory leaks and potential resource exhaustion. An attacker could potentially exploit this vulnerability to exhaust system resources, causing a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.15 of the Linux Kernel by commit 091a4f91942a4396c67e5747f5cb38c6396d1fc5 and has been fixed in version v5.18.13 by commit a91522b4279bebb098106a19b91f82b9c3213be9.

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 specific workaround mentioned for this vulnerability.

Conclusion

The refcount leak vulnerability in intel_dp_add_mst_connector() in the Kernel could potentially lead to a denial-of-service (DoS) condition. It is recommended to update the Linux Kernel to version v5.18.13 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven. However, it could potentially lead to a denial-of-service (DoS) condition by exhausting system resources.

You can use Vulert's 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 provide real-time monitoring and alerts for open-source vulnerabilities.

Yes, the vulnerability has been fixed in version v5.18.13 of the Linux Kernel. It is recommended to update to this version or later to mitigate the risk.

No specific workaround has been mentioned for this vulnerability. It is best to update to the fixed version of the Linux Kernel.

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