Refcount Leak in irqchip/gic-v3

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004839: irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions. Affects Kernel versions >= e3825ba1af3a27d7522c9f5f929f5a13b8b138ae, < e824482e2c5edacc961b7dd30a92fd47606c3036. 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 package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware, software, and processes. The irqchip/gic-v3 module is responsible for managing the Generic Interrupt Controller (GIC) version 3, which is commonly used in ARM-based systems. The GIC is crucial for handling interrupts and ensuring proper communication between hardware devices and the operating system. However, a vulnerability has been discovered in the gic_populate_ppi_partitions function, which can lead to a refcount leak.

Vulnerability Detail

The refcount leak vulnerability in irqchip/gic-v3's gic_populate_ppi_partitions function allows an attacker to cause a memory leak by repeatedly calling this function without properly releasing the allocated resources. This can result in a depletion of available memory, leading to system instability or denial of service. The vulnerability was introduced in version v4.7 of the Linux Kernel and was fixed in version v4.19.249. The impact and attack plausibility of this vulnerability have not been proven yet.

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

As a workaround, users can manually apply the patch provided in the commit e824482e2c5edacc961b7dd30a92fd47606c3036 to their existing Kernel version. The patch modifies the gic_populate_ppi_partitions function to properly release the allocated resources, preventing the refcount leak. Here is an example of the patch:

- // Vulnerable code
+ // Patched code
+ void gic_populate_ppi_partitions()
+ {
+     // Code to properly release allocated resources
+ }

Conclusion

The refcount leak vulnerability in irqchip/gic-v3's gic_populate_ppi_partitions function can lead to memory leaks and potential system instability or denial of service. It is crucial to update the Linux Kernel to version v4.19.249 or later to fix this vulnerability. Alternatively, users can apply the provided patch as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a refcount leak, causing a depletion of available memory. This can result in system instability or denial of service.

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 Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

At the time of this report, no known exploits for this vulnerability have been identified. However, it is important to apply the recommended fix or workaround to mitigate any potential risks.

The exact attack vector and remote exploitability of this vulnerability have not been proven yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.

The recommended solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, users can manually apply the provided patch to their existing Kernel version as a temporary workaround.

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