Heimdall Security Logo

CVE-2026-89494

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, <77686fa5bba135252d348e2dacf481fc19f60c41, <a8facb1670b4a0612183198e758d9539ef628ed9, <50c4cc9183e11f83427efbf770f54851f4471c02, <=5.10.*, <=6.6.*, <dce05b17db862f47ff60614017abe639b2e71cad, 6.6.157, <0e999d56917f861f97adb961617b1828c9eb4733, 2.6.16, <f33041906885f96e190cde54e61ddc69de39e3ee, <=6.18.*, <b54e03d9b3697d25f4a0063cf717d459c5e3ad94, <=7.2.*, <4a5798253212093b9ff7d90c6cfbe348bcda1594, <=*, <=5.15.*, 6.18.50, <2.6.16, 6714d8e86bf443f6f7af50f9d432025649f091f5, 6.12.109, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate lengths in dlm_mig_lockres_handler A node receiving a DLM_MIG_LOCKRES message trusts several fields of the peer-supplied dlm_migratable_lockres without validation. num_locks and lockname_len are bounded only on the sending side, and the message is never checked to actually carry num_locks migratable_lock entries. As a result dlm_process_recovery_data() walks mres->ml[0..num_locks) past the kmalloc(data_len) copy of the message (an out-of-bounds read that ends in a BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the fixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). Both are reachable by any node in the domain. Validate these fields right after dlm_grab(), before anything uses them -- including the not-joined error path, which already prints mres->lockname with the unbounded lockname_len as a %.*s precision. Reject the message unless lockname_len <= DLM_LOCKID_NAME_MAX, num_locks <= DLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the payload is large enough to hold the claimed locks. Conforming recovery and migration messages are unaffected.

Gravité et risque d'exploitation

CVE-2026-89494 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.71 %, ce qui la place devant 52.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, <77686fa5bba135252d348e2dacf481fc19f60c41, <a8facb1670b4a0612183198e758d9539ef628ed9, <50c4cc9183e11f83427efbf770f54851f4471c02, <=5.10.*, <=6.6.*, <dce05b17db862f47ff60614017abe639b2e71cad, 6.6.157, <0e999d56917f861f97adb961617b1828c9eb4733, 2.6.16, <f33041906885f96e190cde54e61ddc69de39e3ee, <=6.18.*, <b54e03d9b3697d25f4a0063cf717d459c5e3ad94, <=7.2.*, <4a5798253212093b9ff7d90c6cfbe348bcda1594, <=*, <=5.15.*, 6.18.50, <2.6.16, 6714d8e86bf443f6f7af50f9d432025649f091f5, 6.12.109, 7.3) 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