CVE-2026-80633

iommufd: Take dma_resv lock before dma_buf_unpin() in release path

Published Aug 28, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

iommufd: Take dma_resv lock before dma_buf_unpin() in release path

dma_buf_unpin() requires the caller to hold the exporter's dma_resv
lock:

void dma_buf_unpin(struct dma_buf_attachment *attach)
{
...
dma_resv_assert_held(dmabuf->resv);
...
}

iopt_release_pages() calls dma_buf_unpin() without taking that lock,
so every iommufd_ioas_destroy()/iommufd_ioas_unmap() that releases
the last reference on a DMABUF-backed iopt_pages triggers a WARN.
This was hit while running tools/testing/selftests/iommu/iommufd:

WARNING: drivers/dma-buf/dma-buf.c:1137 at dma_buf_unpin+0x62/0x70
RIP: 0010:dma_buf_unpin+0x62/0x70
Call Trace:
<TASK>
dma_buf_unpin+0x62/0x70
iopt_release_pages+0xe4/0x190
iopt_unmap_iova_range+0x1c7/0x290
iopt_unmap_all+0x1a/0x30
iommufd_ioas_destroy+0x1d/0x50
iommufd_fops_release+0x93/0x150
__fput+0xfc/0x2c0
__x64_sys_close+0x3d/0x80
do_syscall_64+0x65/0x180
</TASK>

Take the dma_resv lock around dma_buf_unpin() in iopt_release_pages(),
matching the iopt_map_dmabuf() convention. dma_buf_detach() acquires the
reservation lock internally, so it must remain outside the locked region.

Analysis

AI-generated

Technical impact

The Linux kernel’s iommu/iommufd subsystem fails to acquire the dma_resv lock before calling dma_buf_unpin in the release path. dma_buf_unpin requires the lock and will assert if it is not held, resulting in a kernel warning and exposing a race condition that can corrupt shared state or trigger a crash when multiple threads release pages concurrently. This flaw can destabilize the kernel without directly leaking data or providing control to an attacker.

Affected Systems

All Linux kernels containing the iommu/iommufd code before the commits that added the missing lock are potentially affected. Coverage includes mainstream distributions, as the vendor list is unspecified, meaning any distribution kernel compiled with the iommu framework and utilizing DMABUF‑backed iopt_pages that has not applied the patch remains vulnerable.

Risk and Exploitability

The likely attack vector is local, requiring an attacker to perform a release operation such as unmapping or closing an iommufd‑backed device that holds a DMABUF reference. Because the flaw exists only in the release path, it cannot be triggered remotely and requires the attacker to have write privileges to the relevant device. The EPSS score is below 1%, indicating a very low but nonzero probability of exploitation. The CVSS score of 8.8 indicates a high severity flaw that could lead to a kernel crash or denial‑of‑service if repeatedly invoked. The vulnerability is not listed in the CISA KEV catalog, meaning no widespread exploitation has been reported yet.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a release that includes the commits that add the dma_resv lock before dma_buf_unpin.
  • If a vendor update is unavailable, apply the patch manually by cherry‑picking the relevant commits into the current kernel source and rebuild the kernel.
  • Monitor kernel logs for WARN messages from dma_buf_unpin or iopt_release_pages; if they appear, the system is still using the vulnerable code path and the patch should be applied immediately.

Generated by OpenCVE AI on August 31, 2026 at 15:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-362
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'}

Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommufd: Take dma_resv lock before dma_buf_unpin() in release path dma_buf_unpin() requires the caller to hold the exporter's dma_resv lock: void dma_buf_unpin(struct dma_buf_attachment *attach) { ... dma_resv_assert_held(dmabuf->resv); ... } iopt_release_pages() calls dma_buf_unpin() without taking that lock, so every iommufd_ioas_destroy()/iommufd_ioas_unmap() that releases the last reference on a DMABUF-backed iopt_pages triggers a WARN. This was hit while running tools/testing/selftests/iommu/iommufd: WARNING: drivers/dma-buf/dma-buf.c:1137 at dma_buf_unpin+0x62/0x70 RIP: 0010:dma_buf_unpin+0x62/0x70 Call Trace: <TASK> dma_buf_unpin+0x62/0x70 iopt_release_pages+0xe4/0x190 iopt_unmap_iova_range+0x1c7/0x290 iopt_unmap_all+0x1a/0x30 iommufd_ioas_destroy+0x1d/0x50 iommufd_fops_release+0x93/0x150 __fput+0xfc/0x2c0 __x64_sys_close+0x3d/0x80 do_syscall_64+0x65/0x180 </TASK> Take the dma_resv lock around dma_buf_unpin() in iopt_release_pages(), matching the iopt_map_dmabuf() convention. dma_buf_detach() acquires the reservation lock internally, so it must remain outside the locked region.
Title iommufd: Take dma_resv lock before dma_buf_unpin() in release path
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 29, 2026, 6:21 AM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Aug 29, 2026, 7:16 AM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM