CVE-2025-38722habanalabs: fix UAF in export_dmabuf()
- 7.8HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 5 months later
· 5 months later
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < 5b0c23e9ec3e161a893d6ff9b4fad479e4539627
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < d26058c2349d77d1ef179a2cc9752ca12004b6ff
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < c07886761fd6251db6938d4e747002e3d150d231
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < 40deceb38f9db759772d1c289c28fd2a543f57fc
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < 55c232d7e0241f1d5120b595e7a9de24c75ed3d8
- affected db1a8dd916aac986871f6b873a3aefad906f383a – < 33927f3d0ecdcff06326d6e4edb6166aed42811c
- affected 5.16
- unaffected < 5.16
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.43 – ≤ 6.12.*
- unaffected 6.15.11 – ≤ 6.15.*
- unaffected 6.16.2 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References6
- https://git.kernel.org/stable/c/5b0c23e9ec3e161a893d6ff9b4fad479e4539627 (opens in a new tab)
- https://git.kernel.org/stable/c/d26058c2349d77d1ef179a2cc9752ca12004b6ff (opens in a new tab)
- https://git.kernel.org/stable/c/c07886761fd6251db6938d4e747002e3d150d231 (opens in a new tab)
- https://git.kernel.org/stable/c/40deceb38f9db759772d1c289c28fd2a543f57fc (opens in a new tab)
- https://git.kernel.org/stable/c/55c232d7e0241f1d5120b595e7a9de24c75ed3d8 (opens in a new tab)
- https://git.kernel.org/stable/c/33927f3d0ecdcff06326d6e4edb6166aed42811c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-26747 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38722)Record last updated .