CVE-2026-97618

Description

A flaw was found in the Linux kernel's io_uring subsystem. This vulnerability allows a local user to cause a denial of service (DoS) or buffer corruption. When handling network receive operations configured with the packet truncation flag (MSG_TRUNC), the kernel calculates buffer consumption based on the total packet length instead of the bytes actually copied into the buffer. This mismatch causes io_uring to advance the buffer ring past the filled region, resulting in overconsumption of buffers and potential system instability.

Statement

An io_uring receive operation using MSG_TRUNC can incorrectly consume the full reported packet length from a provided buffer ring even when only part of the packet was copied. This can advance the ring beyond the buffers that were actually filled, prematurely consume available entries, and cause ENOBUFS, dropped messages, or disruption of the receiving application. A remote peer may trigger the condition by sending packets larger than the selected buffers when a network service uses io_uring provided buffer rings, incremental buffer consumption, and MSG_TRUNC. For the CVSS the PR:N value is used because an attacker only needs network access to an already configured vulnerable service and does not need a local account on the target. The required io_uring configuration and application behavior make the attack conditional and support AC:H. Impact is primarily limited denial of service. The paranoid score includes limited integrity impact because incorrect buffer accounting may cause message loss or application level data misassociation, but there is no demonstrated UAF, OOB access, arbitrary write, kernel crash, or privilege escalation primitive.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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 Score2.9N/AN/A
Attack VectorLocalN/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 ImpactLowN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.

Access Control,Other

Technical Impact: Bypass Protection Mechanism; Other

In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.

Frequently Asked Questions

Want to get errata notifications? Sign up here.