CVE-2025-38722

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.15.*, db1a8dd916aac986871f6b873a3aefad906f383a, <55c232d7e0241f1d5120b595e7a9de24c75ed3d8, <=6.12.*, 6.12.43, <=*, 5.16, <5.16, <c07886761fd6251db6938d4e747002e3d150d231, <=6.16.*, <33927f3d0ecdcff06326d6e4edb6166aed42811c, 6.17, 0, 6.15.11, 6.16.2, <40deceb38f9db759772d1c289c28fd2a543f57fc

Description

In the Linux kernel, the following vulnerability has been resolved: habanalabs: fix UAF in export_dmabuf() As soon as we'd inserted a file reference into descriptor table, another thread could close it. That's fine for the case when all we are doing is returning that descriptor to userland (it's a race, but it's a userland race and there's nothing the kernel can do about it). However, if we follow fd_install() with any kind of access to objects that would be destroyed on close (be it the struct file itself or anything destroyed by its ->release()), we have a UAF. dma_buf_fd() is a combination of reserving a descriptor and fd_install(). habanalabs export_dmabuf() calls it and then proceeds to access the objects destroyed on close. In particular, it grabs an extra reference to another struct file that will be dropped as part of ->release() for ours; that "will be" is actually "might have already been". Fix that by reserving descriptor before anything else and do fd_install() only when everything had been set up. As a side benefit, we no longer have the failure exit with file already created, but reference to underlying file (as well as ->dmabuf_export_cnt, etc.) not grabbed yet; unlike dma_buf_fd(), fd_install() can't fail.

Gravité et risque d'exploitation

CVE-2025-38722 obtient un score CVSS de 7.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.16 %, ce qui la place devant 4.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.15.*, db1a8dd916aac986871f6b873a3aefad906f383a, <55c232d7e0241f1d5120b595e7a9de24c75ed3d8, <=6.12.*, 6.12.43, <=*, 5.16, <5.16, <c07886761fd6251db6938d4e747002e3d150d231, <=6.16.*, <33927f3d0ecdcff06326d6e4edb6166aed42811c, 6.17, 0, 6.15.11, 6.16.2, <40deceb38f9db759772d1c289c28fd2a543f57fc) 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