CVE-2026-90162

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.8 · Élevée
EPSS 0.6%
Linux•Linux•Versions : <ff6870cf3b7eccc69d03cbb6f23e3995d96e9a8d, 7.2.6, <=*, 6.18.57, 5.15, <29f74f0f2e6df3b393b7b66e810136d0c64e3c59, <=6.18.*, 7.3, 0, <=7.2.*, <5.15, e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, <a1d26dfb32919088e3638dca01068df3c4507433

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: defer publishing granted locks to prevent UAF/double-free race In smb2_lock(), mid-batch granted locks are published to connection-wide (conn->lock_list) and file-wide (fp->lock_list) lists immediately upon vfs_lock_file() success, while also remaining tracked on the stack-local rollback_list. If a subsequent element in the same SMB2_LOCK request array fails validation or execution, the thread jumps to out: and walks rollback_list to undo previously granted locks. However, because the granted lock was already published to conn->lock_list, a concurrent UNLOCK request on the same connection can find the lock object and kfree() it before the rollback loop executes. When the granting thread subsequently walks rollback_list, it dereferences and frees the already-freed ksmbd_lock structure, resulting in a Use-After-Free and Double-Free (on both ksmbd_lock and struct file_lock). Fix this by deferring the publication of granted locks to conn->lock_list and fp->lock_list until after the entire array of lock elements has been processed without error. Mid-batch grants remain tracked exclusively on the request-local rollback_list until the whole batch succeeds, eliminating the race window.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <ff6870cf3b7eccc69d03cbb6f23e3995d96e9a8d, 7.2.6, <=*, 6.18.57, 5.15, <29f74f0f2e6df3b393b7b66e810136d0c64e3c59, <=6.18.*, 7.3, 0, <=7.2.*, <5.15, e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, <a1d26dfb32919088e3638dca01068df3c4507433) 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