Refcount Leak in icp_opal_init() in powerpc/xics

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003738: powerpc/xics: fix refcount leak in icp_opal_init(). Affects Kernel versions < 537a317e5ff45d1f5a0ecaf6a0d7c8043c878cb1. 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 powerpc/xics package is a component of the Linux Kernel, which is responsible for handling interrupt controller operations on PowerPC systems. The icp_opal_init() function in this package initializes the interrupt controller for Open Firmware-based systems. This vulnerability in icp_opal_init() leads to a refcount leak, which can result in resource exhaustion and potential denial of service attacks.

Vulnerability Detail

The vulnerability in icp_opal_init() is caused by a refcount leak, where the reference count of a resource is not properly decremented when it is no longer needed. This can lead to resource exhaustion, as the leaked references are not released, causing a gradual depletion of available resources. An attacker could potentially exploit this vulnerability to exhaust system resources, leading to a denial of service condition. The vulnerability has been fixed in Linux Kernel version v5.4.198 by commit 537a317e5ff45d1f5a0ecaf6a0d7c8043c878cb1.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.198 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to release an updated package containing the fix.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The vulnerability in icp_opal_init() in powerpc/xics can lead to resource exhaustion and potential denial of service attacks. It is recommended to update the Linux Kernel to version v5.4.198 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

The vulnerability can lead to resource exhaustion and potential denial of service attacks.

You can check the Linux Kernel version installed on your system. If it is earlier than v5.4.198, your system may be affected.

No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

There are no known exploits for this vulnerability at the time of this report.

More details about the fix can be found in the commit 537a317e5ff45d1f5a0ecaf6a0d7c8043c878cb1 in the Linux Kernel repository.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.198 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to release an updated package containing the fix.

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.