CVE-2026-99568

Description

A flaw was found in the Linux kernel's I/O Memory Management Unit file descriptor (iommufd) subsystem. Missing bounds checking in the I/O Virtual Address (IOVA) bitmap handler allows memory to be written beyond intended boundaries when tracking dirty memory pages across large page table entries. A local user could exploit this vulnerability by submitting misaligned tracking requests, potentially leading to kernel memory corruption or a Denial of Service (DoS).

Statement

This vulnerability is rated as an Important severity flaw because an authenticated local attacker with access to the kernel's I/O memory management interface could achieve arbitrary out-of-bounds memory writes, potentially compromising the host kernel or crashing the system. In typical Red Hat Enterprise Linux environments, interaction with the iommufd subsystem is restricted to administrative processes or specialized virtualization workloads handling hardware device passthrough. Exploitation requires active usage of dirty page tracking features across large page mappings, meaning unprivileged users lacking device access cannot trigger this vulnerability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.8N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.