CVE-2026-80932

Description

A flaw was found in the Linux kernel, specifically within the vsock/virtio component. An incorrect order of flushing work items during the removal of a virtio_vsock object can lead to a use-after-free condition. This vulnerability allows a race condition where memory can be freed while still in use, potentially resulting in memory corruption and system instability or a denial of service.

Statement

A MODERATE-severity use-after-free flaw was found in the Linux kernel vsock/virtio transport. When a virtio_vsock device is removed, virtio_vsock_remove() flushes its work items in an order that does not account for dependencies between them: tx_work may queue send_pkt_work, and send_pkt_work may in turn queue rx_work. If rx_work is flushed before send_pkt_work queues it again, nothing waits for the newly queued rx_work before the virtio_vsock object is freed, so kfree(vsock) can race with the still-running rx_work. This race can result in a slab use-after-free (as reported by KASAN), leading to memory corruption and a kernel crash or denial of service. Exploitation requires local privileged access to trigger removal of a virtio_vsock device, which limits the practical impact to system availability.

The kernel and kernel-rt packages in Red Hat Enterprise Linux 7, 8, 9, and 10 and the RHCOS kernels shipped with OpenShift Container Platform 4 are marked affected. Red Hat Enterprise Linux 6 is not affected because the vulnerable code is not present in that stream. For the affected streams the fix is deferred: the flaw is rated MODERATE with a Red Hat CVSS 3.1 score of 5.5, below the threshold at which Red Hat files trackers for MODERATE kernel flaws without a higher CVSS score. The residual risk of deferral is a local denial of service through memory corruption during virtio_vsock device removal. The CVE.org score of 8.4 is higher than Red Hat's 5.5 mainly because Red Hat assesses that local privileges are required to trigger the device removal (PR:L) and that the security impact is limited to availability (C:N/I:N/A:H).

Mitigation

Mitigation for this issue is either not available or the currently available options do not 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 Score5.5N/A8.4
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability

Technical Impact: Modify Application Data; Modify Memory; DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands

Attackers may be able to exploit a signal handler race condition to cause the product state to be corrupted. It may be possible to execute arbitrary code by modifying global variables or data structures at unexpected times, violating the assumptions of code that uses this global data.

Access Control

Technical Impact: Gain Privileges or Assume Identity

If a signal handler interrupts code that is executing with privileges, it may be possible that the signal handler will also be executed with elevated privileges, possibly making subsequent exploits more severe.

Frequently Asked Questions

Want to get errata notifications? Sign up here.