CVE-2026-99657

Description

A flaw was found in the Linux kernel. In the Memory Management Unit (MMU) notifier component, an internal tracking reference is set prior to validating memory ranges. A local attacker can exploit this flaw by providing an invalid or wrapping user pointer range, causing registration to fail while leaving tracking data in an inconsistent state. Consequently, subsequent driver cleanup routines attempt to release an unregistered notifier, leading to a system crash and Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate impact for Red Hat because successful exploitation requires local user access and cannot compromise confidentiality or integrity, being limited to a denial of service via a kernel panic. The defect arises during improper state cleanup when handling malformed address ranges in memory management notifier hooks, predominantly exposed when user-space applications request buffer objects through graphics drivers like Radeon. Standard enterprise server installations generally run headless without legacy GPU hardware or direct rendering access granted to untrusted accounts, significantly diminishing the practical attack surface across typical deployments.

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.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/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:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.