# CVE-2026-53322: vfio/pci: Clean up DMABUFs before disabling function

> A race condition in the Linux kernel VFIO PCI driver allows accessing disabled device memory, potentially leading to privilege escalation or data exposure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2026
- **Updated:** 9 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-53322, GHSA-rj34-crxv-j5mg, UBUNTU-CVE-2026-53322

## What is CVE-2026-53322?

CVE-2026-53322 is a high-severity vulnerability in Linux kernel, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

vfio/pci: Clean up DMABUFs before disabling function

On device shutdown, make vfio_pci_core_close_device() call
vfio_pci_dma_buf_cleanup() before the function is disabled via
vfio_pci_core_disable().  This ensures that all access via DMABUFs is
revoked before the function's BARs become inaccessible.

This fixes an issue where, if the function is disabled first, a tiny
window exists in which the function's MSE is cleared and yet BARs
could still be accessed via the DMABUF.  The resources would also be
freed and up for grabs by a different driver.

Weakness: CWE-826 (Premature Release of Resource During Expected Lifetime), CWE-415 (Double Free)

## Which versions are affected by CVE-2026-53322?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53322?

Apply the vendor's patch.

## Is CVE-2026-53322 being exploited?

There is no known exploitation of CVE-2026-53322 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53322 and fix it if it is affected.

What it is: CVE-2026-53322 is a high-severity vulnerability in Linux kernel, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53322 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53322/ (Markdown: https://insights.sbomify.com/CVE-2026-53322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53322
- OSV: https://osv.dev/vulnerability/CVE-2026-53322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53322/
Summaries are generated and may contain mistakes; the official description above is the record.