md/raid1: Fix stack memory use after return in raid1_reshape
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ afeee514ce7f4cab605beedd03be71ebaf0c5fc8 · < 776e6186dc9ecbdb8a1b706e989166c8a99bbf64| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's md/raid1 reshape code can leave a memory-pool wait queue pointing to stack memory after the function returns. Later RAID1 read or write activity can access that invalid address and cause a kernel panic. The input does not specify an attack path or authentication requirements.
Engineers running Linux kernels that use md/raid1 should check whether their kernel includes the fix; affected versions are not specified.