Vulnerability in Kernel package: powerpc/32s: Fix kasan_init_region() for KASAN

Kernel Updated 02 Oct 2025

Summary

18/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000253: powerpc/32s: Fix kasan_init_region() for KASAN. Affects Kernel versions >= 7974c4732642f710b5111165ae1f7f7fed822282, < db37befafa536d1eed293fa5765ad781c3152071. 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 Kernel package is a crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The powerpc/32s architecture is specifically designed for 32-bit PowerPC processors. The kasan_init_region() function is responsible for initializing the Kernel Address Sanitizer (KASAN) for a specific memory region. KASAN is a dynamic memory error detector that helps identify and mitigate memory-related vulnerabilities. However, a vulnerability has been discovered in the implementation of kasan_init_region() for powerpc/32s architecture.

Vulnerability Detail

The vulnerability in powerpc/32s architecture's kasan_init_region() function can potentially be exploited by attackers to trigger memory corruption or execute arbitrary code. The issue arises due to a flaw in the implementation, which can lead to incorrect initialization of the KASAN memory region. This could result in memory access errors, information leaks, or privilege escalation. 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 temporary workaround, users can apply the patch provided in the commit db37befafa536d1eed293fa5765ad781c3152071. The patch modifies the kasan_init_region() function to ensure correct initialization of the KASAN memory region. Here is the code snippet for the patch:

- // Original code
- kasan_init_region(region, start, size);

+ // Patched code
+ if (kasan_enabled()) {
+   kasan_init_region(region, start, size);
+ } else {
+   // Handle initialization without KASAN
+ }

Conclusion

In conclusion, a vulnerability has been identified in the powerpc/32s architecture's kasan_init_region() function of the Kernel package. This vulnerability can potentially lead to memory corruption, information leaks, or privilege escalation. It is crucial to update the Kernel package to the latest version to mitigate the risk. Applying the provided patch or using tools like Vulert can help identify and address the vulnerability. For additional support, 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 exploitation scenario. It could potentially lead to memory corruption, information leaks, or privilege escalation, allowing attackers to gain unauthorized access or execute arbitrary code.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation. Simply upload your package-lock.json file to the Vulert Playground and it will provide information on any vulnerabilities detected.

As of now, there are no known exploits for this vulnerability. However, it is important to apply the necessary patches and updates to mitigate the risk of potential exploitation.

The exact attack vector and remote exploitability of this vulnerability have not been determined yet. It is advisable to update the Kernel package to the latest version as a precautionary measure.

For further support and assistance with vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you in addressing the issue.

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