CVE-2026-72020

Description

A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. When a new connection is created from a malformed synchronization message, certain TCP sequence number fields may not be properly initialized. This can lead to forwarded packets containing stale data in their TCP sequence and acknowledgment numbers, potentially corrupting the TCP flow. A remote attacker could exploit this to disrupt network traffic.

Statement

This vulnerability is evaluated as a Moderate severity issue because it requires a specific, non-default configuration where the IP Virtual Server (IPVS) synchronization daemon is actively processing replication messages alongside application helpers. In typical Red Hat Enterprise Linux installations, IPVS connection synchronization services are disabled by default. Successful exploitation depends on an attacker's ability to inject crafted synchronization payloads into the backup daemon network, restricting the risk profile to clusters actively utilizing state synchronization.

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 Score7N/A9.8
Attack VectorLocalN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.