CVE-2026-99786

Description

A flaw was found in the Linux kernel's xfrm subsystem. A race condition between concurrent IPsec (Internet Protocol Security) policy updates and packet policy lookups can cause the kernel to traverse stale list pointers or miss moved policies. An attacker sending network traffic while policies are being modified could trigger this flaw, resulting in incorrect policy evaluation and potentially allowing network traffic to bypass intended security policies.

Statement

This vulnerability is rated as having a Moderate impact because exploiting the race condition requires highly specific timing between packet processing and concurrent IPsec policy modifications, resulting in a low probability of successful policy evasion. Red Hat Enterprise Linux systems are only exposed if IPsec is actively configured and dynamic policy changes occur concurrently with network traffic evaluation. Systems that do not use IPsec or that maintain static security policies without runtime reconfigurations are not affected by this flaw.

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.8N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

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

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.