Skip to main content
VulnerabilityPublished Updated

CVE-2025-38445: Linux kernel · md/raid1: Fix stack memory use after return in raid1_reshape

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in df5894014a92ff0196dbc212a7764e97366fd2b7 : patch Linux kernel soon.

Data as of 5 Nov 2026, 21:20 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in df5894014a92ff0196dbc212a7764e97366fd2b7, d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98, d8a6853d00fbaa810765c8ed2f452a5832273968 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < df5894014a92ff0196dbc212a7764e97366fd2b7
Fixed in
  • df5894014a92ff0196dbc212a7764e97366fd2b7
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98
Fixed in
  • d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < d8a6853d00fbaa810765c8ed2f452a5832273968
Fixed in
  • d8a6853d00fbaa810765c8ed2f452a5832273968
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < 776e6186dc9ecbdb8a1b706e989166c8a99bbf64
Fixed in
  • 776e6186dc9ecbdb8a1b706e989166c8a99bbf64
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < 61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb
Fixed in
  • 61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb
LinuxLinuxAffected
  • ≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8, < 48da050b4f54ed639b66278d0ae6f4107b2c4e2d
Fixed in
  • 48da050b4f54ed639b66278d0ae6f4107b2c4e2d

AI-suggested

A fix is available in the Linux kernel as indicated by multiple fixed commit versions. Users should update to a Linux kernel version that includes the fix referenced by the commit hashes provided. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's md/raid1 subsystem involves improper use of stack memory in the raid1_reshape function. The function assigns a stack-allocated mempool_t variable to conf->r1bio_pool, causing conf->r1bio_pool.wait.head to point to a stack address. Subsequent access to this invalid address can lead to a kernel panic. The issue is fixed by reinitializing conf->r1bio_pool.wait after assigning newpool.

References

Community reviews

Loading reviews…