CVE-2026-99598

Description

A flaw was found in the Linux kernel's MIPS SGI-IP32 platform code. During Peripheral Component Interconnect (PCI) configuration read operations, modifying the MACE PCI control register can trigger an unsafe sequence of register reads and writes. Under heavy Direct Memory Access (DMA) traffic, this access sequence can cause the system controller to hang. A local user could exploit this vulnerability during PCI device configuration queries to cause a system lockup, resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as having a Moderate impact because triggering the system hang requires local access under active DMA workloads and is strictly limited to specialized MIPS SGI IP32 hardware. Red Hat Enterprise Linux does not support or distribute kernels for the MIPS architecture, meaning the affected PCI controller code is neither compiled nor shipped in Red Hat products. Consequently, standard Red Hat enterprise environments are not exposed to this denial-of-service flaw.

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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity,Confidentiality,Other

Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic

If access to a shared resource is not synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.