cve.bz

CVE-2025-68232 linux linux

7.5 highEPSS 0.4%Fix available

High (7.5) in linux linux. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: veth: more robust handing of race to avoid txq getting stuck Commit dc82a33297fc ("veth: apply qdisc backpressure on full ptr_ring to reduce TX drops") introduced a race condition that can lead to a permanently stalled TXQ. This was observed in production on ARM64 systems (Ampere Altra Max). The race occurs in veth_xmit(). The producer observes a full ptr_ring and stops the queue (netif_tx_stop_queue()). The subsequent conditional logic, intended to re-wake the queue if the consumer had just emptied it (if (__ptr_ring_empty(...)) netif_tx_wake_queue()), can fail. This leads to a "lost wakeup" where the TXQ remains stopped (QUEUE_STATE_DRV_XOFF) and traffic halts. This failure is caused by an incorrect use of the __ptr_ring_empty() API from the producer side. As noted in kernel comments, this check is not guaranteed to be correct if a consumer is operating on another CPU. The empty test is based on ptr_ring->consumer_head, making it reliable only for the consumer. Using this check from the producer side is fundamentally racy. This patch fixes the race by adopting the more robust logic from an earlier version V4 of the patchset, which always flushed the peer: (1) In veth_xmit(), the racy conditional wake-up logic and its memory barrier are removed. Instead, after stopping the queue, we unconditionally call __veth_xdp_flush(rq). This guarantees that the NAPI consumer is scheduled, making it solely responsible for re-waking the TXQ. This handles the race where veth_poll() consumes all packets and completes NAPI *before* veth_xmit() on the producer side has called netif_tx_stop_queue. The __veth_xdp_flush(rq) will observe rx_notify_masked is false and schedule NAPI. (2) On the consumer side, the logic for waking the peer TXQ is moved out of veth_xdp_rcv() and placed at the end of the veth_poll() function. This placement is part of fixing the race, as the netif_tx_queue_stopped() check must occur after rx_notify_masked is potentially set to false during NAPI completion. This handles the race where veth_poll() consumes all packets, but haven't finished (rx_notify_masked is still true). The producer veth_xmit() stops the TXQ and __veth_xdp_flush(rq) will observe rx_notify_masked is true, meaning not starting NAPI. Then veth_poll() change rx_notify_masked to false and stops NAPI. Before exiting veth_poll() will observe TXQ is stopped and wake it up.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68232 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68232?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68232?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68232 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68232

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68232](https://cve.bz/cve/badge/CVE-2025-68232.svg)](https://cve.bz/cve/CVE-2025-68232)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68232"><img src="https://cve.bz/cve/badge/CVE-2025-68232.svg" alt="CVE-2025-68232"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.176.17.10
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.17.10-1DEBIAN-CVE-2025-68232
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68232
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68232
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68232
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68232
Ubuntu24.04:LTSlinux-aws-6.176.17.0-1009.9~24.04.2UBUNTU-CVE-2025-68232 USN-8094-1
Ubuntu24.04:LTSlinux-azure-6.176.17.0-1010.10~24.04.1UBUNTU-CVE-2025-68232 USN-8094-4
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1009.9~24.04.3UBUNTU-CVE-2025-68232 USN-8094-2
Ubuntu24.04:LTSlinux-hwe-6.176.17.0-19.19~24.04.2UBUNTU-CVE-2025-68232 USN-8094-1
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68232
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1017.17UBUNTU-CVE-2025-68232 USN-8152-1
Ubuntu24.04:LTSlinux-oracle-6.176.17.0-1009.9~24.04.1UBUNTU-CVE-2025-68232 USN-8094-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 moreno fix listedUBUNTU-CVE-2025-68232
8 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68232

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A denial of service flaw of moderate impact was found in the Linux kernel's virtual Ethernet (veth) driver. A race condition in the veth_xmit() function, caused by an incorrect producer-side use of the __ptr_ring_empty() API, can result in a "lost wakeup" in which the transmit queue remains permanently stopped and network traffic through the veth device halts. Triggering the race requires an actor with local access able to generate traffic through an affected veth pair (veth devices are commonly used for container and virtual machine networking), and the impact is limited to availability, with no effect on confidentiality or integrity. Red Hat assessed this flaw as Moderate severity with a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower than the upstream CVE.org score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), because triggering the issue requires local access and traffic through a veth device rather than an unauthenticated remote vector. The vulnerable code, introduced upstream by commit dc82a33297fc ("veth: apply qdisc backpressure on full ptr_ring to reduce TX drops"), is not present in the Red Hat Enterprise Linux 7, 8, 9, and 10 kernel and kernel-rt update streams or in Red Hat In-Vehicle OS 1.1, so those products are not affected; the remaining Red Hat Enterprise Linux 6 ELS relationship is out of support scope.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68232.

References

Check your stackJSON