CVE-2026-53322: vfio/pci: Clean up DMABUFs before disabling function
Noroxi assessment
Priority: Monitor (action score 35/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.13% (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 4f1000a30f67cf7d328059242776a858611d5ef9, d97708701434ce72968e771976aaf9d3438fcafd.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4f1000a30f67cf7d328059242776a858611d5ef9, d97708701434ce72968e771976aaf9d3438fcafd 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: 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.
- Published
- Jun 26, 2026
- Updated
- Sep 9, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-415
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
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 helpAffected 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 kernel6.19 and later · before 7.0.10
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
- 6.19affected
- 5d74781ebc86c5fa9e9d6934024c505412de9b52 and later · before 4f1000a30f67cf7d328059242776a858611d5ef9affected · git
- 5d74781ebc86c5fa9e9d6934024c505412de9b52 and later · before d97708701434ce72968e771976aaf9d3438fcafdaffected · git
- before 6.19not affected · semver
- 7.0.10 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53319Jun 26, 2026 · blk-wbt: remove WARN_ON_ONCE from wbt_init_enable_default()22Monitor
- ← EarlierCVE-2026-53320Jun 26, 2026 · nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty()22Monitor
- Later →CVE-2026-53323Jun 26, 2026 · net: dsa: remove redundant netdev_lock_ops() from conduit ethtool ops22Monitor
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 | 4f1000a30f67cf7d328059242776a858611d5ef9 | Vendor (CNA) |
| Linux Linux | d97708701434ce72968e771976aaf9d3438fcafd | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 7.0.10-1 · Debian:14 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:kernel | 0:6.12.0-211.53.1.el10_2 · Rocky Linux:10 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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.
- CVE-2026-529932 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-6388823 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
- CVE-2026-6438429 days apartsmb: client: fix change notify replay double-free39Monitor
- CVE-2026-6438529 days apartsmb: client: fix double-free in SMB2_ioctl() replay39Monitor
- CVE-2026-6438629 days apartsmb: client: fix query_info() replay double-free39Monitor
- CVE-2026-6438729 days apartsmb: client: fix query directory replay double-free39Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0454 · Jun 29, 2026(Linux Kernel Güvenlik Bildirimi)
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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.