Refcount Leak in gic_populate_ppi_partitions in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004299: irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions. Affects Kernel versions >= e3825ba1af3a27d7522c9f5f929f5a13b8b138ae, < c136c2924a59a399aa789858cfb320d481964fb7. 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 fundamental component of the Linux operating system that manages core system functions, including hardware communication and resource allocation. It provides an interface between software applications and the computer's hardware. The gic_populate_ppi_partitions function is part of the irqchip/gic-v3 module in the Kernel, which handles interrupt handling for ARM-based systems. This function is responsible for populating the private peripheral interrupt (PPI) partitions in the Generic Interrupt Controller (GIC) version 3. The GIC is a hardware component that manages interrupts in ARM-based systems. The vulnerability in gic_populate_ppi_partitions can lead to a refcount leak, which can result in resource exhaustion and potential denial-of-service attacks.

Vulnerability Detail

The vulnerability in gic_populate_ppi_partitions arises from a refcount leak. When the function is called, it fails to properly release the reference count on certain resources, leading to a leak. This can result in resource exhaustion, as the leaked references are not properly freed. An attacker could potentially exploit this vulnerability to exhaust system resources, leading to a denial-of-service condition. The vulnerability was introduced in version 4.7 of the Linux Kernel and was fixed in version 5.18.6. The fix involves correcting the refcount handling in the gic_populate_ppi_partitions function.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the Linux Kernel to version 5.18.6 or later. This can be done by downloading the latest stable version of the Kernel from the official Git repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. Alternatively, users can check if their system is affected by the vulnerability using the Vulert Playground (https://vulert.com/scanner) without requiring access to the code or installation.

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 gic_populate_ppi_partitions in the Kernel can lead to resource exhaustion and potential denial-of-service attacks. It is recommended to update the Linux Kernel to version 5.18.6 or later to fix this vulnerability. Users can also use the Vulert Playground to check if their system is affected without requiring access to the code or installation. 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 resource exhaustion and potential denial-of-service attacks.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected without requiring access to the code or installation.

Yes, the vulnerability has been fixed in Linux Kernel version 5.18.6.

Yes, you can manually fix this vulnerability by updating the Linux Kernel to version 5.18.6 or later.

There are no known exploits for this vulnerability at the moment.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the Linux Kernel to version 5.18.6 or later. This can be done by downloading the latest stable version of the Kernel from the official Git repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. Alternatively, users can check if their system is affected by the vulnerability using the Vulert Playground (https://vulert.com/scanner) without requiring access to the code or installation.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.