CVE-2026-53372

Description

A flaw was found in the Linux kernel's Input/Output Memory Management Unit (IOMMU) subsystem. This vulnerability arises in virtualized environments when a nested domain attempts to attach to a Process Address Space ID (PASID), a mechanism for devices to access memory, while its parent domain is configured for dirty page tracking. The kernel lacks proper dirty tracking support for the nested domain in this scenario, leading to a failure in attachment and the potential loss of dirty pages. This can result in data integrity issues or system instability within the virtualized environment.

Statement

Intel VT-d allowed PASID attachment to a nested IOMMU domain even when the stage 2 parent domain had dirty tracking configured. The kernel does not support dirty tracking for this nested PASID configuration, so DMA writes may be missed in the dirty bitmap and dirty guest pages may be lost during migration or snapshot style workflows. For the CVSS the PR:L is used in the paranoid score because a delegated VM management service or reduced capability virtualization role may be able to request PASID attachment and dirty tracking without full host administrator control. The issue is not directly network reachable and does not indicate host memory corruption. Impact is mainly integrity loss for migrated VM state or workload data rather than direct host privilege escalation.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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 Score5.35.5N/A
Attack VectorLocalLocalN/A
Attack ComplexityHighLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneNoneN/A
Integrity ImpactLowNoneN/A
Availability ImpactHighHighN/A

Vector

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

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

Understanding the Weakness (CWE)

Integrity,Availability

Technical Impact: DoS: Crash, Exit, or Restart; Unexpected State

This could lead to instability, incorrect behavior, or a vulnerability. Any data that was produced as a result of a function call could be in a bad state upon return. If the return value is not checked, then this bad data may be used in operations, possibly leading to a crash or other unintended behaviors.

Frequently Asked Questions

Want to get errata notifications? Sign up here.