Vulnerability in Kernel: bus: qcom: Put child node before return

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000474: bus: qcom: Put child node before return. Affects Kernel versions >= 335a127548081322bd2b294d715418648912f20c, < 94810fc52925eb122a922df7f9966cf3f4ba7391. 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 Kernel is a critical component of the Linux operating system that manages communication between hardware and software. It provides essential functions and services for the proper functioning of the system. The bus subsystem in the Kernel handles device communication and configuration. The qcom driver is responsible for managing Qualcomm devices. This vulnerability specifically affects the qcom driver in the Kernel.

Vulnerability Detail

The vulnerability in the qcom driver occurs when a child node is not properly released before returning from a function. This can lead to resource leaks and potential memory corruption. An attacker may be able to exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. The vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v4.14.233.

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. It is recommended to apply the fix by updating the Kernel to the latest version.

Conclusion

The vulnerability in the Kernel's qcom driver can lead to resource leaks and potential memory corruption. It is recommended to update the Linux Kernel to version v4.14.233 or later to fix this vulnerability. Regularly updating the Kernel is crucial for maintaining the security of the system. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can potentially allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service condition.

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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

Yes, a patch has been released in version v4.14.233 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.

The exact exploitability of this vulnerability depends on various factors, including the system configuration and network setup. However, in general, an attacker would need local access to the system to exploit this vulnerability.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the patch as soon as possible to mitigate any potential risks.

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