CVE-2026-53312

iommu/riscv: Remove overflows on the invalidation path

Published Jun 26, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

iommu/riscv: Remove overflows on the invalidation path

Since RISC-V supports a sign extended page table it should support
a gather->end of ULONG_MAX, but if this happens it will infinite loop
because of the overflow.

Also avoid overflow computing the length by moving the +1 to the other
side of the <

Analysis

AI-generated

Technical impact

The Linux kernel contains an integer overflow in the IOMMU invalidation path on RISC‑V architectures. When a sign‑extended page table reaches ULONG_MAX, adding one to that value wraps, causing the kernel to enter an endless loop while walking the table. The infinite loop locks the thread that performs the invalidation, effectively denying service to processes that depend on IOMMU operations.

Affected Systems

Linux kernel versions on RISC‑V hardware that use the IOMMU subsystem with sign‑extended page tables are affected. Any kernel build before the commits listed in the references (40a13b4, 9f0632b, e4b7687) contains the flaw, regardless of specific sub‑release numbers.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity, while the EPSS score of less than 1% suggests a low likelihood of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires triggering an IOMMU invalidation, which a local privileged user or an attacker controlling a device could influence. The risk is medium for systems that regularly perform IOMMU invalidations and do not have mitigations in place.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install a Linux kernel release that contains the patch commits that remove the overflow on RISC‑V IOMMU invalidation.
  • If an updated kernel cannot be applied immediately, disable the IOMMU subsystem on RISC‑V CPUs that are not required for normal operation to prevent the infinite loop from occurring.
  • Restart any services that depend on IOMMU after patching or disabling the subsystem, and monitor kernel logs for signs of the infinite loop or abnormal CPU usage.

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8566-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8568-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
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
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-190
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommu/riscv: Remove overflows on the invalidation path Since RISC-V supports a sign extended page table it should support a gather->end of ULONG_MAX, but if this happens it will infinite loop because of the overflow. Also avoid overflow computing the length by moving the +1 to the other side of the <
Title iommu/riscv: Remove overflows on the invalidation path
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jun 26, 2026, 7:41 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Analyzed
Published
Jun 26, 2026, 8:17 PM
Modified
Jul 6, 2026, 8:13 PM
Severity
Public date
Jun 26, 2026, 12:00 AM