CVE-2025-38445
Description
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.
How to fix
- linux linux_kernel5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or later
- git.kernel.org/stable/c/12b00ec99624f8da8c325f2dd6e807df26df0025
- git.kernel.org/stable/c/48da050b4f54ed639b66278d0ae6f4107b2c4e2d
- git.kernel.org/stable/c/5f35e48b76655e45522df338876dfef88dafcc71
- git.kernel.org/stable/c/61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb
- git.kernel.org/stable/c/776e6186dc9ecbdb8a1b706e989166c8a99bbf64
- git.kernel.org/stable/c/d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98
- git.kernel.org/stable/c/d8a6853d00fbaa810765c8ed2f452a5832273968
- git.kernel.org/stable/c/df5894014a92ff0196dbc212a7764e97366fd2b7
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 4.18 ≤ v < 5.4.296, 5.5 ≤ v < 5.10.240, 5.11 ≤ v < 5.15.189, 5.16 ≤ v < 6.1.146, 6.2 ≤ v < 6.6.99, 6.7 ≤ v < 6.12.39, 6.13 ≤ v < 6.15.7, 6.16 | 5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 |
| debian debian_linux | 11.0 | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.