Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 12b00ec99624f8da8c325f2dd6e807df26df0025, 48da050b4f54ed639b66278d0ae6f4107b2c4e2d, 5f35e48b76655e45522df338876dfef88dafcc71; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 12b00ec99624f8da8c325f2dd6e807df26df0025, 48da050b4f54ed639b66278d0ae6f4107b2c4e2d, 5f35e48b76655e45522df338876dfef88dafcc71; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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->r1bio_pool. This results in conf->r1bio_pool.wait.head pointing to a stack address. Accessing this address later can lead to a kernel panic. Example access path: raid1_reshape() { // newpool is on the stack mempool_t newpool, oldpool; // initialize newpool.wait.head to stack address mempool_init(&newpool, ...); conf->r1bio_pool = newpool; } raid1_read_request() or raid1_write_request() { alloc_r1bio() { mempool_alloc() { // if pool->alloc fails remove_element() { --pool->curr_nr; } } } } mempool_free() { if (pool->curr_nr < pool->min_nr) { // pool->wait.head is a stack address // wake_up() will try to access this invalid address // which leads to a kernel panic return; wake_up(&pool->wait); } } Fix: reinit conf->r1bio_pool.wait after assigning newpool.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jul 25, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38445

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.240
  • linux linux kernel5.11 and later · before 5.15.189
  • linux linux kernel5.16 and later · before 6.1.146
  • linux linux kernel4.18 and later · before 5.4.296
  • linux linux kernel6.7 and later · before 6.12.39
  • linux linux kernel6.13 and later · before 6.15.7
  • linux linux kernel6.2 and later · before 6.6.99
  • linux linux kernel6.16

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.18affected
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before d8a6853d00fbaa810765c8ed2f452a5832273968affected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before 12b00ec99624f8da8c325f2dd6e807df26df0025affected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before 48da050b4f54ed639b66278d0ae6f4107b2c4e2daffected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before 5f35e48b76655e45522df338876dfef88dafcc71affected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before df5894014a92ff0196dbc212a7764e97366fd2b7affected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before 776e6186dc9ecbdb8a1b706e989166c8a99bbf64affected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before 61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdbaffected · git
    • afeee514ce7f4cab605beedd03be71ebaf0c5fc8 and later · before d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98affected · git
    • before 4.18not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.147-16.1.147-1
Debian:13linuxbefore 6.12.41-16.12.41-1
Debian:14linuxbefore 6.16.3-16.16.3-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38443Jul 25, 2025 · nbd: fix uaf in nbd_genl_connect() error path
    31Monitor
  • ← EarlierCVE-2025-38444Jul 25, 2025 · raid10: cleanup memleak at raid10_make_request
    22Monitor
  • Later →CVE-2025-38446Jul 25, 2025 · clk: imx: Fix an out-of-bounds access in dispmix_csr_clk_dev_data
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux12b00ec99624f8da8c325f2dd6e807df26df0025Vendor (CNA)
Linux Linux48da050b4f54ed639b66278d0ae6f4107b2c4e2dVendor (CNA)
Linux Linux5f35e48b76655e45522df338876dfef88dafcc71Vendor (CNA)
Linux Linux61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdbVendor (CNA)
Linux Linux776e6186dc9ecbdb8a1b706e989166c8a99bbf64Vendor (CNA)
Linux Linuxd67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98Vendor (CNA)
Linux Linuxd8a6853d00fbaa810765c8ed2f452a5832273968Vendor (CNA)
Linux Linuxdf5894014a92ff0196dbc212a7764e97366fd2b7Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records