CVE-2025-71225: md: suspend array while updating raid_disks via sysfs
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22, 165d1359f945b72c5f90088f60d48ff46115269e, 2cc583653bbe050bacd1cadcc9776d39bf449740; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22, 165d1359f945b72c5f90088f60d48ff46115269e, 2cc583653bbe050bacd1cadcc9776d39bf449740; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 18, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-367
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.4.59 and later · before 3.5
- linux linux kernel3.9.7 and later · before 3.10
- linux linux kernel3.10.1 and later · before 6.12.70
- linux linux kernel6.13 and later · before 6.18.10
- linux linux kernel3.10
- linux linux kernel6.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76, 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9, 3.10affected
- e2d59925221cd562e07fee38ec8839f7209ae603 and later · before 863b9b7be824a6b2c0587532d3ece3022c6dd451affected · git
- e2d59925221cd562e07fee38ec8839f7209ae603 and later · before 165d1359f945b72c5f90088f60d48ff46115269eaffected · git
- e2d59925221cd562e07fee38ec8839f7209ae603 and later · before 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22affected · git
- e2d59925221cd562e07fee38ec8839f7209ae603 and later · before 2cc583653bbe050bacd1cadcc9776d39bf449740affected · git
- 3.4.59 and later · before 3.5affected · semver
- 3.9.7 and later · before 3.10affected · semver
- before 3.10not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.70 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.10-1 | 6.18.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23228Feb 18, 2026 · smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()22Monitor
- ← EarlierCVE-2026-23229Feb 18, 2026 · crypto: virtio - Add spinlock protection with virtqueue notification22Monitor
- Later →CVE-2025-71227Feb 18, 2026 · wifi: mac80211: don't WARN for connections on invalid channels22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22 | Vendor (CNA) |
| Linux Linux | 165d1359f945b72c5f90088f60d48ff46115269e | Vendor (CNA) |
| Linux Linux | 2cc583653bbe050bacd1cadcc9776d39bf449740 | Vendor (CNA) |
| Linux Linux | 3.10 | Vendor (CNA) |
| Linux Linux | 3.5 | Vendor (CNA) |
| Linux Linux | 863b9b7be824a6b2c0587532d3ece3022c6dd451 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.73-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-38352211 days apartposix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV61This week
- CVE-2026-64091151 days apartbatman-adv: tt: fix TOCTOU race for reported vlans39Monitor
- CVE-2026-64034151 days apartnet: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer37Monitor
- CVE-2026-63937151 days apartKVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer35Monitor
- CVE-2026-63867151 days apartmptcp: close TOCTOU race while computing rcv_wnd32Monitor
- CVE-2026-3167866 days apartopenvswitch: defer tunnel netdev_put to RCU release31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.