Answer in brief
CVE-2025-38445 records a High severity (CVSS 7.1) vulnerability in md/raid1: Fix stack memory use after return in raid1_reshape. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <d8a6853d00fbaa810765c8ed2f452a5832273968 || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <12b00ec99624f8da8c325f2dd6e807df26df0025 || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <48da050b4f54ed639b66278d0ae6f4107b2c4e2d || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <5f35e48b76655e45522df338876dfef88dafcc71 || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <df5894014a92ff0196dbc212a7764e97366fd2b7 || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <776e6186dc9ecbdb8a1b706e989166c8a99bbf64 || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb || >=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98 | d8a6853d00fbaa810765c8ed2f452a5832273968, 12b00ec99624f8da8c325f2dd6e807df26df0025, 48da050b4f54ed639b66278d0ae6f4107b2c4e2d, 5f35e48b76655e45522df338876dfef88dafcc71, df5894014a92ff0196dbc212a7764e97366fd2b7, 776e6186dc9ecbdb8a1b706e989166c8a99bbf64, 61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb, d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98 |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.