ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-38722

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

Published Sep 4, 2025 · catalog updated Oct 21, 2026 · linux kernel

Check this week

CVE-2025-38722 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run linux kernel.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
16.00%
Remediation
Version ranges on file
Affected products
cpe linux/linux kernel · vendor Linux Linux db1a8dd916aac986871f6b873a3aefad906f383a <33927f3d0ecdcff06326d6e4edb6166aed42811c

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe linux/linux kernel6.17
  • cpe linux/linux kernel< 6.12.43
  • cpe linux/linux kernel< 6.15.11
  • cpe linux/linux kernel< 6.16.2
  • vendor Linux Linux db1a8dd916aac986871f6b873a3aefad906f383a <33927f3d0ecdcff06326d6e4edb6166aed42811cdb1a8dd916aac986871f6b873a3aefad906f383a <33927f3d0ecdcff06326d6e4edb6166aed42811c

How to fix CVE-2025-38722

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-38722 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run linux kernel.

Which versions are affected?

Compare what you have installed with linux/linux kernel 6.17; linux/linux kernel < 6.12.43; linux/linux kernel < 6.15.11; linux/linux kernel < 6.16.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-416: Use After Free. EPSS 16.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 4, 2025 · NIST NVD

    Detected

    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

  2. Oct 19, 2026 · NIST NVD

    Updated

    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

  3. Oct 21, 2026 · NIST NVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2025-38722

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2025-26747

    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 t

    euvd.enisa.europa.eu
  • NIST NVDVulnerability recordCVE-2025-38722

    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 descripto

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.