Vulnerability in phy: qcom-qmp package: fix reset-controller leak on probe errors

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003297: phy: qcom-qmp: fix reset-controller leak on probe errors. Affects Kernel versions >= e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, < ba173a6f8d8dffed64bb13ab23081bdddfb464f0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The phy: qcom-qmp package is a component of the Linux Kernel ecosystem. It provides support for Qualcomm QMP (Qualcomm Message Passing) PHYs. These PHYs are responsible for managing communication between different hardware components in Qualcomm SoCs (System on Chips). The package is crucial for ensuring proper functioning and communication within the system.

Vulnerability Detail

The vulnerability in the phy: qcom-qmp package involves a reset-controller leak on probe errors. When the package encounters errors during the probe process, it fails to release the reset-controller, leading to a resource leak. This vulnerability can potentially result in resource exhaustion and system instability. It was introduced in version v4.12 of the Linux Kernel and has been fixed in version v5.15.46.

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 vulnerability in the phy: qcom-qmp package can result in resource exhaustion and system instability. It is crucial to update the Linux Kernel to version v5.15.46 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 resource exhaustion and system instability due to the reset-controller leak on probe errors.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you in real-time if the vulnerability is detected.

As of now, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to prevent any potential exploitation.

No, the recommended fix for this vulnerability is to update the Linux Kernel to version v5.15.46 or later. Manually fixing the issue without updating the Kernel may not address the root cause and could lead to further complications.

No, the fix for this vulnerability is specific to the phy: qcom-qmp package in the Linux Kernel. It is recommended to update the Kernel to the fixed version to ensure the package functions correctly.

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