CVE-2026-64152

Description

A flaw was found in the Linux kernel's Input/Output Memory Management Unit (IOMMU) subsystem when iommu_debug is enabled. This issue occurs because an error handling path attempts to unmap memory without a proper initial mapping, leading to an inconsistent state within the IOMMU's debugging and tracing mechanisms. This malfunction could result in unbalanced tracking, potentially affecting system stability or the accuracy of IOMMU debugging information.

Mitigation

To mitigate this issue in Red Hat In-Vehicle OS, ensure that the `iommu_debug` kernel parameter is not enabled. This can typically be achieved by verifying that `iommu_debug` is not present in the kernel command line arguments during boot. Disabling this debug feature may impact diagnostic capabilities but will prevent the vulnerable code path from being exercised. A system reboot is required for changes to kernel boot parameters to take effect.

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.1N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AChanged
ConfidentialityHighN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability,Other

Technical Impact: DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands; Modify Memory; Other

Depending on the locking functionality, an unlock of a non-locked resource might corrupt the state of the product, possibly including denial of service, memory corruption, or other modification to the resource (or its associated metadata that is used for tracking locks). In some cases, an unlock operation might not have any adverse effects.

Frequently Asked Questions

Want to get errata notifications? Sign up here.