Correct Bitmap Allocation Size in powerpc/xive/spapr

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004166: powerpc/xive/spapr: correct bitmap allocation size. Affects Kernel versions < 99d1c36bddd93919072b5a51a89297bbb5ad6a6f. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The powerpc/xive/spapr package is a component of the Linux Kernel, which is responsible for handling interrupt virtualization for PowerPC systems. It provides support for the XIVE interrupt controller in the SPAPR (Server Platform Architecture for Power) platform. The XIVE interrupt controller manages interrupt distribution and prioritization for virtual machines running on PowerPC systems. This vulnerability affects the bitmap allocation size in the powerpc/xive/spapr package.

Vulnerability Detail

The vulnerability in the powerpc/xive/spapr package relates to an incorrect bitmap allocation size. This issue could potentially lead to memory corruption or other security vulnerabilities. Attackers may be able to exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial-of-service condition. The vulnerability has been identified and fixed in the Linux Kernel version v5.18.13 by commit 99d1c36bddd93919072b5a51a89297bbb5ad6a6f.

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.18.13 or later. This can be done by applying the commit 99d1c36bddd93919072b5a51a89297bbb5ad6a6f to the kernel source code. Detailed instructions on how to update the Linux Kernel can be found in the official documentation or community resources.

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

In conclusion, the powerpc/xive/spapr package in the Linux Kernel is vulnerable to an incorrect bitmap allocation size issue. This vulnerability could potentially lead to memory corruption or other security vulnerabilities. It is recommended to update the Linux Kernel to version v5.18.13 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

This vulnerability could potentially lead to memory corruption or other security vulnerabilities. Attackers may be able to exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial-of-service condition.

Yes, this vulnerability has been fixed in the Linux Kernel version v5.18.13 by commit 99d1c36bddd93919072b5a51a89297bbb5ad6a6f.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.18.13 or later. This can be done by applying the commit 99d1c36bddd93919072b5a51a89297bbb5ad6a6f to the kernel source code. Detailed instructions on how to update the Linux Kernel can be found in the official documentation or community resources.

There are no specific workarounds mentioned for this vulnerability.

More information about this vulnerability can be found in the references link provided in the vulnerability details.

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.18.13 or later. This can be done by applying the commit 99d1c36bddd93919072b5a51a89297bbb5ad6a6f to the kernel source code. Detailed instructions on how to update the Linux Kernel can be found in the official documentation or community resources.

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.