| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025090400-CVE-2025-38722-de5f@gregkh> Date: Thu, 4 Sep 2025 17:33:27 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() From: Greg Kroah-Hartman <gregkh@...nel.org> 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. The Linux kernel CVE team has assigned CVE-2025-38722 to this issue. Affected and fixed versions =========================== Issue introduced in 5.16 with commit db1a8dd916aac986871f6b873a3aefad906f383a and fixed in 6.12.43 with commit c07886761fd6251db6938d4e747002e3d150d231 Issue introduced in 5.16 with commit db1a8dd916aac986871f6b873a3aefad906f383a and fixed in 6.15.11 with commit 40deceb38f9db759772d1c289c28fd2a543f57fc Issue introduced in 5.16 with commit db1a8dd916aac986871f6b873a3aefad906f383a and fixed in 6.16.2 with commit 55c232d7e0241f1d5120b595e7a9de24c75ed3d8 Issue introduced in 5.16 with commit db1a8dd916aac986871f6b873a3aefad906f383a and fixed in 6.17-rc2 with commit 33927f3d0ecdcff06326d6e4edb6166aed42811c Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-38722 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/accel/habanalabs/common/memory.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/c07886761fd6251db6938d4e747002e3d150d231 https://git.kernel.org/stable/c/40deceb38f9db759772d1c289c28fd2a543f57fc https://git.kernel.org/stable/c/55c232d7e0241f1d5120b595e7a9de24c75ed3d8 https://git.kernel.org/stable/c/33927f3d0ecdcff06326d6e4edb6166aed42811c
Powered by blists - more mailing lists