CVE-2026-99352

Description

A flaw was found in the Linux kernel's SUNRPC (Remote Procedure Call) subsystem. A remote attacker can cause a Denial of Service (DoS) by initiating and rapidly closing network connections to an RPC-based service. This issue occurs because accepted transport structures are published before internal trace logging completes, leading to a race condition where one thread frees the connection data while another reads it. This use-after-free condition can result in an unexpected kernel crash.

Statement

This vulnerability is rated as Moderate severity because successful exploitation depends on winning a tight race condition against kernel RPC server threads, with the primary consequence being a denial of service (system crash) rather than remote code execution. Under typical Red Hat Enterprise Linux deployments, kernel RPC transport handling is only exposed when services like the NFS server are actively configured and listening for network connections. Furthermore, the issue specifically affects transport tracepoint handling, which is inactive under standard default system configurations, significantly reducing practical exposure during normal operation.

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.9N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/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:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.