CVE-2026-99800

Description

A flaw was found in the Linux kernel's io_uring subsystem. A race condition can occur when a secondary task completes or cleans up a request while the owning process exits, causing the task context to be freed prematurely while still being accessed. A local user could exploit this vulnerability to cause a use-after-free condition, potentially leading to privilege escalation or a Denial of Service (DoS) via a kernel crash.

Statement

This vulnerability is rated as an Important severity flaw because an unprivileged local attacker could leverage the memory corruption flaw to achieve arbitrary code execution in kernel space or cause an immediate system crash. Although exploitation requires local execution privileges to invoke asynchronous I/O operations, the ability to compromise kernel integrity without administrative privileges elevates the impact above Moderate. Systems that disallow unprivileged access to the io_uring interface or operate in environments where unprivileged user access is restricted have a significantly reduced attack surface.

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 Score7.8N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: 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

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.