CVE-2026-99734

Description

A flaw was found in the Linux kernel's shared memory (shmem) subsystem. When validating shared memory files, the kernel verified memory mapping properties rather than confirming the underlying inode type. A local user could exploit this flaw by manipulating file mappings to cause the kernel to access an unexpected inode type during file sealing or memory descriptor operations. This can lead to memory corruption, system instability, or a denial of service (DoS).

Statement

This vulnerability is rated Moderate rather than Important because successful exploitation requires local authenticated access with complex memory-mapping conditions and is limited to a denial of service without compromising data integrity or confidentiality. An attacker must construct uncommon file mapping scenarios involving wrapper filesystem constructs to trigger type confusion when handling shared memory file seals. Standard enterprise installations do not typically encounter these conditions during normal operation, constraining the overall blast radius.

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)

Other

Technical Impact: Varies by Context

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.

Availability,Integrity,Confidentiality

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

If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.