Medium 5.3Published Feb 18, 2026

CVE-2025-71225md: suspend array while updating raid_disks via sysfs

Updated under an hour ago (Oct 27, 2026, 10:30 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 5.3 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H
Weakness (CWE): CWE-362
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from e2d59925221cd562e07fee38ec8839f7209ae603 before 863b9b7be824a6b2c0587532d3ece3022c6dd451; from e2d59925221cd562e07fee38ec8839f7209ae603 before 165d1359f945b72c5f90088f60d48ff46115269e; from e2d59925221cd562e07fee38ec8839f7209ae603 before 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22; from e2d59925221cd562e07fee38ec8839f7209ae603 before 2cc583653bbe050bacd1cadcc9776d39bf449740; 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76; 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9; from 3.4.59 before 3.5; from 3.9.7 before 3.10	CNA record
linux linux_kernel linux:linux_kernel	from 3.4.59 before 3.5; from 3.9.7 before 3.10; from 3.10.1 before 6.12.70; from 6.13 before 6.18.10; 3.10; 3.10; 3.10; 6.19; and 2 more ranges	NVD

References

References

https://git.kernel.org/stable/c/863b9b7be824a6b2c0587532d3ece3022c6dd451
https://git.kernel.org/stable/c/165d1359f945b72c5f90088f60d48ff46115269e	patch
https://git.kernel.org/stable/c/0107b18cd8ac17eb3e54786adc05a85cdbb6ef22	patch
https://git.kernel.org/stable/c/2cc583653bbe050bacd1cadcc9776d39bf449740	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.