CVE-2026-90388

iommu/dma: Check atomic pool allocation result directly

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

iommu/dma: Check atomic pool allocation result directly

The non-blocking, non-coherent allocation path uses dma_alloc_from_pool(),
which returns the allocated page and fills cpu_addr only on success.

Do not rely on cpu_addr to detect allocation failure in this path. Check
the returned page directly before using it for the IOMMU mapping.

Analysis

AI-generated

Technical impact

The Linux kernel’s IOMMU DMA allocation code can fault when the non‑blocking, non‑coherent path calls dma_alloc_from_pool(). The routine returns the allocated page only on success and sets cpu_addr accordingly, but the kernel mistakenly uses cpu_addr to detect failure. If cpu_addr is NULL and the returned page is NULL or invalid, the kernel may attempt an IOMMU mapping on an unreachable address, leading to a NULL pointer dereference and an OOPS or kernel panic, which in turn provides a denial of service. The weakness manifests as a classic null‑pointer dereference.

Affected Systems

The flaw resides in all Linux kernel builds that have not yet incorporated the patch found on the kernel git tree. Consequently, every system that runs a current Linux kernel and exercises the iommu/dma non‑blocking allocation path could be affected, including generic servers, embedded devices, and virtualized guests that rely on direct device access.

Risk and Exploitability

The vulnerability has a high CVSS score of 7.8. The EPSS score of less than 1% indicates a low current exploitation probability, and the flaw is not listed in the CISA KEV catalog. An attacker would need to trigger local kernel code execution or load a module that calls dma_alloc_from_pool without checking the returned page. If such an action is performed, the kernel may crash, which in turn results in denial of service. No evidence suggests this leads to privilege escalation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the iommu/dma allocation check fix.
  • If a kernel upgrade cannot be performed immediately, disable or restrict drivers that use the non‑blocking DMA allocation path or enforce stringent code review to validate returned pages before use.
  • Monitor system logs for IOMMU‑related PANIC or OOPS events and investigate anomalous failures promptly.

Generated by OpenCVE AI on September 20, 2026 at 01:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4841-1 linux security update
Debian DSA Debian DSA DSA-6528-1 linux security update
Ubuntu USN Ubuntu USN USN-8961-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9029-1 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-346
CWE-476
Type Values Removed Values Added
Weaknesses CWE-476
Type Values Removed Values Added
Weaknesses CWE-476
Type Values Removed Values Added
Metrics cvssV3_1

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

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommu/dma: Check atomic pool allocation result directly The non-blocking, non-coherent allocation path uses dma_alloc_from_pool(), which returns the allocated page and fills cpu_addr only on success. Do not rely on cpu_addr to detect allocation failure in this path. Check the returned page directly before using it for the IOMMU mapping.
Title iommu/dma: Check atomic pool allocation result directly
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
Oct 19, 2026, 9:02 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 19, 2026, 9:19 AM