Heimdall Security Logo

CVE-2025-21931

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <af288a426c3e3552b62595c6138ec6371a17dbba, 0, <4.21, <4.10, 6.12.19, cb1206e85df291fefde27401190329e26996c54c, 6.14, 6.13.7, <4.20, <=6.6.*, 4.20.2, 5.0, 060853fdd434ce620dd1dd7619ede834bd33b9d0, <629dfc6ba5431056701d4e44830f3409b989955a, <4.5, a2b977e3d9e4298d28ebe5cfff9e0859b74a7ac7, 4.19.15, <93df6da64b004f75d307ed08d3f0f1020280d339, <5.0, 6.1.140, 4.9.150, 3.16.65, 2c87072a3bf9bbcd747618bb2ccc3cd0da181db6, 2c25071bed4b1f9c4cfb10a7914847d7069794bf, 4.4.170, b15c87263a69272423771118c653e9a1d0672caa, 6.6.92, <576a2f4c437c19bec7d05d05b5990f178d2b0f40, 4.14.93, <3926b572fd073491bde13ec42ee08ac1b337bf4d, <=*, <3.17, <4.15, <=6.13.*, 85ef35ab972b7484f41c3bb2bbc79de212e19129

Description

In the Linux kernel, the following vulnerability has been resolved: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined) add page poison checks in do_migrate_range in order to make offline hwpoisoned page possible by introducing isolate_lru_page and try_to_unmap for hwpoisoned page. However folio lock must be held before calling try_to_unmap. Add it to fix this problem. Warning will be produced if folio is not locked during unmap: ------------[ cut here ]------------ kernel BUG at ./include/linux/swapops.h:400! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G W 6.13.0-rc1-00016-g3c434c7ee82a-dirty #41 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0xb08/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0xb08/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000) ---[ end trace 0000000000000000 ]---

Gravité et risque d'exploitation

CVE-2025-21931 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.15 %, ce qui la place devant 4.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <af288a426c3e3552b62595c6138ec6371a17dbba, 0, <4.21, <4.10, 6.12.19, cb1206e85df291fefde27401190329e26996c54c, 6.14, 6.13.7, <4.20, <=6.6.*, 4.20.2, 5.0, 060853fdd434ce620dd1dd7619ede834bd33b9d0, <629dfc6ba5431056701d4e44830f3409b989955a, <4.5, a2b977e3d9e4298d28ebe5cfff9e0859b74a7ac7, 4.19.15, <93df6da64b004f75d307ed08d3f0f1020280d339, <5.0, 6.1.140, 4.9.150, 3.16.65, 2c87072a3bf9bbcd747618bb2ccc3cd0da181db6, 2c25071bed4b1f9c4cfb10a7914847d7069794bf, 4.4.170, b15c87263a69272423771118c653e9a1d0672caa, 6.6.92, <576a2f4c437c19bec7d05d05b5990f178d2b0f40, 4.14.93, <3926b572fd073491bde13ec42ee08ac1b337bf4d, <=*, <3.17, <4.15, <=6.13.*, 85ef35ab972b7484f41c3bb2bbc79de212e19129) 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

Rechercher une autre CVE