CVE-2025-71225

Source
https://cve.org/CVERecord?id=CVE-2025-71225
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71225.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-71225
Downstream
AZL (1)
BELL (1)
CLSA (1)
DEBIAN (1)
ECHO (1)
OESA (3)
openSUSE (1)
ROOT (4)
SUSE (10)
UBUNTU (1)
Related
Published
2026-02-18T14:21:46Z
Modified
2026-10-22T02:47:40Z
Summary
md: suspend array while updating raid_disks via sysfs
Details

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.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71225.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
e2d59925221cd562e07fee38ec8839f7209ae603
Fixed
863b9b7be824a6b2c0587532d3ece3022c6dd451
Fixed
165d1359f945b72c5f90088f60d48ff46115269e
Fixed
0107b18cd8ac17eb3e54786adc05a85cdbb6ef22
Fixed
2cc583653bbe050bacd1cadcc9776d39bf449740
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3.4.59
Fixed
3.5
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3.9.7
Fixed
3.10
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
1b9203bb4c658c0242afa6fdb025c71d2fc3ad76
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9

Affected versions

v3.*
v3.4.100
v3.4.101
v3.4.102
v3.4.103
v3.4.104
v3.4.105
v3.4.106
v3.4.107
v3.4.108
v3.4.109
v3.4.110
v3.4.111
v3.4.112
v3.4.113
v3.4.59
v3.4.60
v3.4.61
v3.4.62
v3.4.63
v3.4.64
v3.4.65
v3.4.66
v3.4.67
v3.4.68
v3.4.69
v3.4.70
v3.4.71
v3.4.72
v3.4.73
v3.4.74
v3.4.75
v3.4.76
v3.4.77
v3.4.78
v3.4.79
v3.4.80
v3.4.81
v3.4.82
v3.4.83
v3.4.84
v3.4.85
v3.4.86
v3.4.87
v3.4.88
v3.4.89
v3.4.90
v3.4.91
v3.4.92
v3.4.93
v3.4.94
v3.4.95
v3.4.96
v3.4.97
v3.4.98
v3.4.99
v3.9.10
v3.9.11
v3.9.7
v3.9.8
v3.9.9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71225.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.10.0
Fixed
6.6.160
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.70
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.10

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71225.json"