Kernel Panic Risk in Linux Package Due to Stack Memory Mismanagement

linux Updated 02 Oct 2025

Summary

25/07/2025
N/A
No i
Unrated
Not published

CVE-2025-38445: In the Linux kernel, the following vulnerability has been resolved: md/raid1: Fix stack memory use after return in raid1_reshape In the raid1_reshape function, newpool is allocated on the stack and assigned to conf->r1bi... Affects linux versions 5.10.103-1 – 6.9.9-1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Linux package is a core component of the Debian operating system, responsible for managing system resources and hardware interactions. It provides essential functionalities that allow the operating system to communicate with hardware devices, manage memory, and execute processes. This vulnerability specifically affects the RAID1 functionality within the Linux kernel, which is crucial for data redundancy and reliability in storage systems.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the raid1_reshape function where a stack-allocated memory pool is improperly assigned to a configuration structure. This leads to a situation where a pointer to a stack address is stored, which can be accessed later, potentially causing a kernel panic. The vulnerability arises from the incorrect handling of memory allocation, where the stack memory is freed upon function return, but the pointer remains valid in the configuration structure, leading to undefined behavior and system crashes.

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

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch as soon as it becomes available.

Conclusion

In summary, CVE-2025-38445 is a critical vulnerability in the Linux kernel that can lead to kernel panics due to improper memory management. It is essential to update your Linux package to the latest version to mitigate this risk. Monitoring tools like Vulert can help keep your applications secure from such vulnerabilities.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-38445 is a vulnerability in the Linux kernel that can lead to a kernel panic due to improper handling of stack memory in the RAID1 functionality.

If exploited, this vulnerability can cause your system to crash unexpectedly, leading to potential data loss and downtime.

The vulnerability affects Linux versions in Debian 11, 12, and 13. You should check your version and apply the necessary updates.

You can use tools like Vulert, which monitors your application for open-source vulnerabilities using just a manifest file like package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

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