CVE-2026-90140

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <6.6.157, <=6.1.*, <=6.12.*, <5.15.221, <4deb3edead0c0e172cc7349e8855d741d3c5e162, 5.15.221, <c40f3f24839f8404325a2099e26c2a04786ae309, 0, a8f650b93e55764ca9ff8e1ddebc151f57024086, 6.1.188, 6.8, 6.18.52, 6.6.48, 053fc4f755ad43cf35210677bcba798ccdc48d0c, <6.8, <a1b46aee33d83f14ed62d7fdef1a91d3e0b732a9, <=6.6.*, 6.6.157, <45ae914b2f6ea56fc2f1c017fdee4e995bcb4c0e, 7.2.6, bfbab62ca69f72bcd14ea30de1fb98f6080ad464, 6.1.107, <ac5c499413385cea3e0220d6050408d50842891d, <=6.18.*, <389bd349ddbcf90dbd8a4f2a4ab6e552d53df134, 6.12.110, <=7.2.*, <7fe415e1cd8fa875be263670c0ab47109818abb6, <=*, <=5.15.*, 535e9bd0e8f8d8cfdc29de7cdb902b5041427fe6, 5.15.166, <6.1.188, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: cuse: wait for pending RCU callbacks on module exit Since commit 053fc4f755ad ("fuse: fix UAF in rcu pathwalks"), fuse_conn_put() frees the fuse_conn through call_rcu() rather than synchronously. For cuse, fc->release is cuse_fc_release(), which lives in the cuse module. If the module is removed before the RCU grace period ends, the callback jumps into freed module memory: userspace / module unload | RCU softirq ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ close(/dev/cuse) | cuse_channel_release() | fuse_dev_release() | fuse_conn_put(fch->conn) | call_rcu(delayed_release) ------+---> callback queued | rmmod cuse | cuse_exit() | cuse_channel_destroy() | ... | return | | <module text freed> | | rcu_do_batch() | delayed_release() | fc->release() | -> cuse_fc_release() | ^^^ freed text! The freed module text is unmapped by vfree(), so the jump into the stale callback triggers a page-fault Oops. If the virtual address is subsequently reused, the callback could execute unrelated code (undefined behaviour). Fix this by calling rcu_barrier() in cuse_exit() so that any pending fuse_conn release callback completes before the module is removed.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <6.6.157, <=6.1.*, <=6.12.*, <5.15.221, <4deb3edead0c0e172cc7349e8855d741d3c5e162, 5.15.221, <c40f3f24839f8404325a2099e26c2a04786ae309, 0, a8f650b93e55764ca9ff8e1ddebc151f57024086, 6.1.188, 6.8, 6.18.52, 6.6.48, 053fc4f755ad43cf35210677bcba798ccdc48d0c, <6.8, <a1b46aee33d83f14ed62d7fdef1a91d3e0b732a9, <=6.6.*, 6.6.157, <45ae914b2f6ea56fc2f1c017fdee4e995bcb4c0e, 7.2.6, bfbab62ca69f72bcd14ea30de1fb98f6080ad464, 6.1.107, <ac5c499413385cea3e0220d6050408d50842891d, <=6.18.*, <389bd349ddbcf90dbd8a4f2a4ab6e552d53df134, 6.12.110, <=7.2.*, <7fe415e1cd8fa875be263670c0ab47109818abb6, <=*, <=5.15.*, 535e9bd0e8f8d8cfdc29de7cdb902b5041427fe6, 5.15.166, <6.1.188, 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