NVD / CVE Program· CNA Linux

CVE-2025-38722: habanalabs: fix UAF in export_dmabuf()

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 33927f3d0ecdcff06326d6e4edb6166aed42811c, 40deceb38f9db759772d1c289c28fd2a543f57fc, 55c232d7e0241f1d5120b595e7a9de24c75ed3d8; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 33927f3d0ecdcff06326d6e4edb6166aed42811c, 40deceb38f9db759772d1c289c28fd2a543f57fc, 55c232d7e0241f1d5120b595e7a9de24c75ed3d8; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-02850

Published: Sep 4, 2025
Updated: Oct 30, 2026
EPSS: 0.2% · 10th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.16 and later · before 6.12.43
linux linux kernel6.13 and later · before 6.15.11
linux linux kernel6.16 and later · before 6.16.2
linux linux kernel6.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.16affected
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before 5b0c23e9ec3e161a893d6ff9b4fad479e4539627affected · git
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before d26058c2349d77d1ef179a2cc9752ca12004b6ffaffected · git
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before c07886761fd6251db6938d4e747002e3d150d231affected · git
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before 40deceb38f9db759772d1c289c28fd2a543f57fcaffected · git
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before 55c232d7e0241f1d5120b595e7a9de24c75ed3d8affected · git
- db1a8dd916aac986871f6b873a3aefad906f383a and later · before 33927f3d0ecdcff06326d6e4edb6166aed42811caffected · git
- before 5.16not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	from 0	—
Debian:13	linux	before 6.12.43-1	6.12.43-1
Debian:14	linux	before 6.16.3-1	6.16.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2025-38720Sep 4, 2025 · net: hibmcge: fix rtnl deadlock issue
22Monitor
← EarlierCVE-2025-38721Sep 4, 2025 · netfilter: ctnetlink: fix refcount leak on table dump
22Monitor
Later →CVE-2025-38723Sep 4, 2025 · LoongArch: BPF: Fix jump offset calculation in tailcall
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	33927f3d0ecdcff06326d6e4edb6166aed42811c	Vendor (CNA)
Linux Linux	40deceb38f9db759772d1c289c28fd2a543f57fc	Vendor (CNA)
Linux Linux	55c232d7e0241f1d5120b595e7a9de24c75ed3d8	Vendor (CNA)
Linux Linux	5b0c23e9ec3e161a893d6ff9b4fad479e4539627	Vendor (CNA)
Linux Linux	c07886761fd6251db6938d4e747002e3d150d231	Vendor (CNA)
Linux Linux	d26058c2349d77d1ef179a2cc9752ca12004b6ff	Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
debian:linux	6.12.43-1 · Debian:13	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/33927f3d0ecdcff06326d6e4edb6166aed42811c

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records