Answer in brief
CVE-2025-71225 records a Unknown severity vulnerability in md: suspend array while updating raid_disks via sysfs. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e2d59925221cd562e07fee38ec8839f7209ae603 <165d1359f945b72c5f90088f60d48ff46115269e || >=e2d59925221cd562e07fee38ec8839f7209ae603 <0107b18cd8ac17eb3e54786adc05a85cdbb6ef22 || >=e2d59925221cd562e07fee38ec8839f7209ae603 <2cc583653bbe050bacd1cadcc9776d39bf449740 || 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76 || 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9 || >=3.4.59 <3.5 || >=3.9.7 <3.10 | 165d1359f945b72c5f90088f60d48ff46115269e, 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22, 2cc583653bbe050bacd1cadcc9776d39bf449740, 3.5, 3.10 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
Feb 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 19, 2026
In the Linux kernel, the following vulnerability has been resolved: md: suspend array while updating raid_disks via sysfs In raid1_reshape(), freeze_array() is called before modifying the r1bio memory pool (conf->r1bio_pool) and conf->raid_disks, and unfreeze_array() is called after the update is completed. However, freeze_array() only waits until nr_sync_pending and (nr_pending - nr_queued) of all buckets reaches zero. When an I/O error occurs, nr_queued is increased and the corresponding r1bio is queued to either retry_list or bio_end_io_list. As a result, freeze_array() may unblock before these r1bios are released. This can lead to a situation where conf->raid_disks and the mempool have already been updated while queued r1bios, allocated with the old raid_disks value, are later released. Consequently, free_r1bio() may access memory out of bounds in put_all_bios() and release r1bios of the wrong size to the new mempool, potentially causing issues with the mempool as well. Since only normal I/O might increase nr_queued while an I/O error occurs, suspending the array avoids this issue. Note: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends the array. Therefore, we suspend the array when updating raid_disks via sysfs to avoid this issue too.
Quoted source text, attributed separately from HOL analysis.