CVE-2025-71225

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 3.9.7, <=6.12.*, <=*, <3.5, 3.10, 6.19, 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76, <=6.18.*, <3.10, 3.4.59, <2cc583653bbe050bacd1cadcc9776d39bf449740, 0, 6.12.70, <0107b18cd8ac17eb3e54786adc05a85cdbb6ef22, 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9, <165d1359f945b72c5f90088f60d48ff46115269e, e2d59925221cd562e07fee38ec8839f7209ae603, 6.18.10

Description

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.

Gravité et risque d'exploitation

CVE-2025-71225 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.10 %, ce qui la place devant 0.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 3.9.7, <=6.12.*, <=*, <3.5, 3.10, 6.19, 1b9203bb4c658c0242afa6fdb025c71d2fc3ad76, <=6.18.*, <3.10, 3.4.59, <2cc583653bbe050bacd1cadcc9776d39bf449740, 0, 6.12.70, <0107b18cd8ac17eb3e54786adc05a85cdbb6ef22, 8ccf6cfb157419847f3cb2bfdfbcdbd39860e8e9, <165d1359f945b72c5f90088f60d48ff46115269e, e2d59925221cd562e07fee38ec8839f7209ae603, 6.18.10) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références