CVE-2025-39939

Description

A flaw was found in the Linux kernel's s390 IOMMU (Input-Output Memory Management Unit) driver. When reporting statistics for devices configured with an identity domain, improper address handling causes an out-of-bounds memory access. A local privileged attacker can exploit this issue during device monitoring to trigger kernel memory corruption, resulting in a Denial of Service (DoS) via a system crash.

Statement

This vulnerability is rated as having a Moderate impact because it is restricted to IBM Z (s390x) platforms and requires local privileged access to trigger identity domain operations on PCI devices. On affected systems, improper pointer handling in the IOMMU statistics reporting routine can result in out-of-bounds memory access and kernel memory corruption during device monitoring. The flaw cannot be exploited remotely and does not affect non-s390 architectures, significantly limiting the exposure.

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.27.87.8
Attack VectorLocalLocalLocal
Attack ComplexityHighLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityLowHighHigh
Integrity ImpactLowHighHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.