CVE-2025-38722 Details
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.
A use-after-free vulnerability has been identified in the Linux kernel's habanalabs component, specifically within the export_dmabuf() function. This issue arises when a file reference is inserted into the descriptor table; another thread could potentially close it. While this scenario is manageable when merely returning the descriptor to userland, it becomes problematic if fd_install() is followed by access to objects that are destroyed upon closure. The vulnerability occurs because export_dmabuf() calls dma_buf_fd(), which combines reserving a descriptor and fd_install(), and then accesses objects that may have already been destroyed. The vulnerability has been addressed by modifying the function to reserve the descriptor before any other actions and to perform fd_install() only after everything is set up, eliminating the previous race condition.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for downloading the patched version are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.16, < 6.12.43 >= 6.13, < 6.15.11 >= 6.16, < 6.16.2 6.17 rc1 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | kernel.org |
| Oct 21, 2026 | CVE Modified | kernel.org |
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 25, 2025 | Initial Analysis | [email protected] |
| Sep 4, 2025 | New CVE Received | kernel.org |