Heimdall Security Logo

CVE-2026-64033

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.5%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, bab17b761c8974a869b04462be5d4dd9aad366b4, <5b74373390113fba798a76b483837029ab010fef, 0, <01e42aabaf7632beb4bf235c7238b96c746d4144, <00904a73272b9f3ef3952fe69a833909dccad1ef, <5.17, 5.15.209, 6.12.92, 6.6.142, <=6.6.*, <92060ab1c5115674cf319175550f85f68405121f, 6.1.175, <b0e9706fb2859064bb6c677554c4d20c713aa8e0, 6.18.34, 7.1, <=6.18.*, 7.0.11, 5.15.61, <eae62c5451e67e8b033c1681fd3b85d7e9a9a28f, ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, <=*, <5.15.209, <=5.15.*, <548f3956e53a7f7bde912d8129010b8986d5e602, 5.17

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrs_srv_create_path_files(), the sysfs root folders may already have been created and srv_path->kobj may already have been initialized. If a later step fails, the cleanup currently calls kobject_put(&srv_path->kobj) before rtrs_srv_destroy_once_sysfs_root_folders(srv_path). kobject_put() may drop the last reference to srv_path->kobj and invoke the release callback, rtrs_srv_release(), which frees srv_path. The following call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then dereferences srv_path internally to access srv_path->srv, resulting in a use-after-free. This failure path is reached before rtrs_srv_create_path_files() returns success, so the successful-path lifetime handling is not involved. Fix this by destroying the sysfs root folders before calling kobject_put(&srv_path->kobj), so srv_path is still valid while the helper accesses it. This issue was found by a static analysis tool I am developing.

Gravité et risque d'exploitation

CVE-2026-64033 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.49 %, ce qui la place devant 40.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, bab17b761c8974a869b04462be5d4dd9aad366b4, <5b74373390113fba798a76b483837029ab010fef, 0, <01e42aabaf7632beb4bf235c7238b96c746d4144, <00904a73272b9f3ef3952fe69a833909dccad1ef, <5.17, 5.15.209, 6.12.92, 6.6.142, <=6.6.*, <92060ab1c5115674cf319175550f85f68405121f, 6.1.175, <b0e9706fb2859064bb6c677554c4d20c713aa8e0, 6.18.34, 7.1, <=6.18.*, 7.0.11, 5.15.61, <eae62c5451e67e8b033c1681fd3b85d7e9a9a28f, ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, <=*, <5.15.209, <=5.15.*, <548f3956e53a7f7bde912d8129010b8986d5e602, 5.17) 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