CVE-2026-99676

Description

A flaw was found in the Linux kernel's networking subsystem. On weakly ordered processor architectures, improper memory barrier ordering during lockless socket reference counting allows socket accesses to be reordered before a reference is securely acquired. An attacker could exploit this race condition during concurrent network socket operations, potentially leading to a Denial of Service (DoS) via a system crash or memory corruption.

Statement

This vulnerability is rated as having a Moderate impact for Red Hat Enterprise Linux because triggering the race condition requires high-complexity timing under weakly ordered hardware architectures, restricting the impact strictly to a denial of service. The underlying issue exists within core kernel networking routines responsible for socket tracking and connection transitions. Because exploitation cannot be leveraged for arbitrary code execution or unauthorized data exposure, the overall severity is limited.

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)

Integrity,Confidentiality,Other

Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic; Unexpected State

If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.