CVE-2025-71225 (GCVE-0-2025-71225)
Vulnerability from cvelistv5 – Published: 2026-02-18 14:21 – Updated: 2026-02-20 11:30
VLAI?
Title
md: suspend array while updating raid_disks via sysfs
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
e2d59925221cd562e07fee38ec8839f7209ae603 , < 165d1359f945b72c5f90088f60d48ff46115269e
(git)
Affected: e2d59925221cd562e07fee38ec8839f7209ae603 , < 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22 (git) Affected: e2d59925221cd562e07fee38ec8839f7209ae603 , < 2cc583653bbe050bacd1cadcc9776d39bf449740 (git) Affected: 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76 (git) Affected: 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9 (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/md/md.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "165d1359f945b72c5f90088f60d48ff46115269e",
"status": "affected",
"version": "e2d59925221cd562e07fee38ec8839f7209ae603",
"versionType": "git"
},
{
"lessThan": "0107b18cd8ac17eb3e54786adc05a85cdbb6ef22",
"status": "affected",
"version": "e2d59925221cd562e07fee38ec8839f7209ae603",
"versionType": "git"
},
{
"lessThan": "2cc583653bbe050bacd1cadcc9776d39bf449740",
"status": "affected",
"version": "e2d59925221cd562e07fee38ec8839f7209ae603",
"versionType": "git"
},
{
"status": "affected",
"version": "1b9203bb4c658c0242afa6fdb025c71d2fc3ad76",
"versionType": "git"
},
{
"status": "affected",
"version": "8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/md/md.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.10"
},
{
"lessThan": "3.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.70",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.19",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.70",
"versionStartIncluding": "3.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.10",
"versionStartIncluding": "3.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19",
"versionStartIncluding": "3.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "3.4.59",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "3.9.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u003er1bio_pool) and conf-\u003eraid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u003eraid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too."
}
],
"providerMetadata": {
"dateUpdated": "2026-02-20T11:30:50.415Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/165d1359f945b72c5f90088f60d48ff46115269e"
},
{
"url": "https://git.kernel.org/stable/c/0107b18cd8ac17eb3e54786adc05a85cdbb6ef22"
},
{
"url": "https://git.kernel.org/stable/c/2cc583653bbe050bacd1cadcc9776d39bf449740"
}
],
"title": "md: suspend array while updating raid_disks via sysfs",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2025-71225",
"datePublished": "2026-02-18T14:21:46.249Z",
"dateReserved": "2026-02-14T16:26:02.969Z",
"dateUpdated": "2026-02-20T11:30:50.415Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2025-71225\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-02-18T15:18:40.330\",\"lastModified\":\"2026-02-18T17:51:53.510\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmd: suspend array while updating raid_disks via sysfs\\n\\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\\nmemory pool (conf-\u003er1bio_pool) and conf-\u003eraid_disks, and\\nunfreeze_array() is called after the update is completed.\\n\\nHowever, freeze_array() only waits until nr_sync_pending and\\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\\noccurs, nr_queued is increased and the corresponding r1bio is queued to\\neither retry_list or bio_end_io_list. As a result, freeze_array() may\\nunblock before these r1bios are released.\\n\\nThis can lead to a situation where conf-\u003eraid_disks and the mempool have\\nalready been updated while queued r1bios, allocated with the old\\nraid_disks value, are later released. Consequently, free_r1bio() may\\naccess memory out of bounds in put_all_bios() and release r1bios of the\\nwrong size to the new mempool, potentially causing issues with the\\nmempool as well.\\n\\nSince only normal I/O might increase nr_queued while an I/O error occurs,\\nsuspending the array avoids this issue.\\n\\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\\nthe array. Therefore, we suspend the array when updating raid_disks\\nvia sysfs to avoid this issue too.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0107b18cd8ac17eb3e54786adc05a85cdbb6ef22\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/165d1359f945b72c5f90088f60d48ff46115269e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/2cc583653bbe050bacd1cadcc9776d39bf449740\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…