Missing Free in wm8350-power Charger IRQ

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002353: power: supply: wm8350-power: Add missing free in free_charger_irq. Affects Kernel versions >= 14431aa0c5a443d13d24e6f865a8838f97dab973, < 60dd1082322966f192f42fe2a6605dfa08eef41f. 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 wm8350-power module is responsible for managing power supply in devices that use the WM8350 power management IC. It provides functionality for charging the device's battery and handling charger-related interrupts. The vulnerability in question pertains to a missing 'free' operation in the 'free_charger_irq' function of the module.

Vulnerability Detail

The missing 'free' operation in the 'free_charger_irq' function can lead to a resource leak. When a charger interrupt is no longer needed, the function is responsible for freeing the associated resources. However, due to the missing 'free' operation, these resources are not properly released, resulting in a potential resource exhaustion issue. An attacker could potentially exploit this vulnerability to exhaust system resources, leading to a denial-of-service condition or other adverse effects.

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 missing 'free' operation in the 'free_charger_irq' function of the wm8350-power module can lead to a resource leak and potential resource exhaustion. To mitigate this vulnerability, it is recommended to update to Linux Kernel version v4.19.238 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the specific usage scenario. It could potentially lead to resource exhaustion, resulting in a denial-of-service condition or other adverse effects.

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

At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply the necessary patches and updates to mitigate any potential risks.

To exploit this vulnerability, an attacker would need to have the ability to trigger charger interrupts in the affected system. This typically requires physical access to the device or some level of control over the charging process.

Yes, this vulnerability has been fixed in Linux Kernel version v4.19.238 by commit 60dd1082322966f192f42fe2a6605dfa08eef41f.

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