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

vfio/pci: Check BAR resources before exporting a DMABUF

A DMABUF exports access to BAR resources and, although they are
requested at startup time, we need to ensure they really were reserved
before exporting. Otherwise, it's possible to access unreserved
resources through the export.

Add a check to the DMABUF-creation path.
Published: 2026-07-19
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This vulnerability allows a malicious actor to create a DMA buffer that references BAR resources which were not verified, permitting the export of DMABUFs that expose unreserved hardware resources. Attackers could read or write to memory ranges intended for exclusive use, potentially leaking sensitive data or corrupting system state. The underlying weakness corresponds to CWE‑1220, a failure to validate external input before use.

Affected Systems

The flaw affects all Linux kernel releases prior to the patch that introduces a check of BAR resources in the DMABUF creation path. Both generic Linux kernels and derivatives that have not applied the commit 702809dabdecca807bdd50cfdcc1c980feb2ba62 are vulnerable. There are no version ranges provided in the advisory, so any kernel lacking this commit is at risk.

Risk and Exploitability

With a CVSS score of 8.8 the vulnerability is classified as high severity, and an EPSS score of less than 1% indicates a low current exploitation probability. The flaw is not listed in the CISA KEV catalog. Based on the description, it is inferred that exploitation likely requires local or privileged access, implying that an attacker must have sufficient kernel or device driver privileges to trigger the flaw.

Generated by OpenCVE AI on August 1, 2026 at 07:40 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the bar resource check (commit 702809dabdecca807bdd50cfdcc1c980feb2ba62).
  • Enforce strict access controls on the vfio subsystem so that only trusted users or services can create and export DMABUFs.
  • If a kernel update is not yet available, disable or restrict the vfio/pci driver to prevent untrusted devices from allocating DMABUFs.

Generated by OpenCVE AI on August 1, 2026 at 07:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Tue, 21 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-1220
References
Metrics threat_severity

None

threat_severity

Important


Mon, 20 Jul 2026 14:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}


Sun, 19 Jul 2026 16:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Check BAR resources before exporting a DMABUF A DMABUF exports access to BAR resources and, although they are requested at startup time, we need to ensure they really were reserved before exporting. Otherwise, it's possible to access unreserved resources through the export. Add a check to the DMABUF-creation path.
Title vfio/pci: Check BAR resources before exporting a DMABUF
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:38:34.964Z

Reserved: 2026-07-19T07:54:57.029Z

Link: CVE-2026-64042

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-64042 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-01T07:45:05Z

Weaknesses
  • CWE-1220

    Insufficient Granularity of Access Control