Heimdall Security Logo

CVE-2025-38681

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <ff40839e018b82c4d756d035f34a63aa2d93be83, bbd6ec605c0fc286c3f8ce60b4ed44635361d58b, <ca8c414499f2e5337a95a76be0d21b728ee31c6b, <=6.16.*, 6.17, 0, <=6.15.*, 6.6.103, <5.7, <=5.10.*, <=6.6.*, 5.15.190, <59305202c67fea50378dcad0cc199dbc13a0e99a, <67995d4244694928ce701928e530b5b4adeb17b4, 6.12.43, 6.1.149, 6.16.2, 5.7, <1636b5e9c3543b87d673e32a47e7c18698882425, 5.10.241, <=*, <=5.15.*, <69bea84b06b5e779627e7afdbf4b60a7d231c76f, 6.15.11, <ac25ec5fa2bf6e606dc7954488e4dded272fa9cd, <3ee9a8c27bfd72c3f465004fa8455785d61be5e8

Description

In the Linux kernel, the following vulnerability has been resolved: mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() Memory hot remove unmaps and tears down various kernel page table regions as required. The ptdump code can race with concurrent modifications of the kernel page tables. When leaf entries are modified concurrently, the dump code may log stale or inconsistent information for a VA range, but this is otherwise not harmful. But when intermediate levels of kernel page table are freed, the dump code will continue to use memory that has been freed and potentially reallocated for another purpose. In such cases, the ptdump code may dereference bogus addresses, leading to a number of potential problems. To avoid the above mentioned race condition, platforms such as arm64, riscv and s390 take memory hotplug lock, while dumping kernel page table via the sysfs interface /sys/kernel/debug/kernel_page_tables. Similar race condition exists while checking for pages that might have been marked W+X via /sys/kernel/debug/kernel_page_tables/check_wx_pages which in turn calls ptdump_check_wx(). Instead of solving this race condition again, let's just move the memory hotplug lock inside generic ptdump_check_wx() which will benefit both the scenarios. Drop get_online_mems() and put_online_mems() combination from all existing platform ptdump code paths.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <ff40839e018b82c4d756d035f34a63aa2d93be83, bbd6ec605c0fc286c3f8ce60b4ed44635361d58b, <ca8c414499f2e5337a95a76be0d21b728ee31c6b, <=6.16.*, 6.17, 0, <=6.15.*, 6.6.103, <5.7, <=5.10.*, <=6.6.*, 5.15.190, <59305202c67fea50378dcad0cc199dbc13a0e99a, <67995d4244694928ce701928e530b5b4adeb17b4, 6.12.43, 6.1.149, 6.16.2, 5.7, <1636b5e9c3543b87d673e32a47e7c18698882425, 5.10.241, <=*, <=5.15.*, <69bea84b06b5e779627e7afdbf4b60a7d231c76f, 6.15.11, <ac25ec5fa2bf6e606dc7954488e4dded272fa9cd, <3ee9a8c27bfd72c3f465004fa8455785d61be5e8) 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