CVE-2026-97611

Description

A flaw was found in the Linux kernel's Open vSwitch subsystem. A race condition during the reallocation of internal flow table structures allows memory to be freed while it is still being accessed by packet processing routines, causing a use-after-free condition. An attacker can exploit this flaw during flow table updates to cause a system crash resulting in a Denial of Service (DoS) or potentially escalate privileges.

Statement

A use after free in the Open vSwitch flow table mask array can occur because tbl_mask_array_realloc() schedules the old array for RCU freeing before publishing the replacement array. A packet lookup entering ovs_flow_tbl_lookup_stats during this preemptible window can acquire the old array after call_rcu has started its grace period. The old array can then be freed while flow_lookup still dereferences it, resulting in a kernel use after free and at least a local denial of service. For the CVSS the PR:L is selected because reliable triggering normally requires the ability to modify Open vSwitch datapath flows or otherwise induce mask array reallocation, which commonly requires CAP_NET_ADMIN or delegated Open vSwitch administration. Packet processing can be influenced by network traffic, but remote traffic alone does not reliably trigger the reallocation race. The confirmed kernel heap UAF creates a plausible worst case risk of confidentiality integrity and privilege impact and should be reviewed manually.

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 Score4.7N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.