CVE-2026-68129
CVE CVE-2026-68129EUVD EUVD-2026-55510Published 2026-08-10T11:58:51.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: gve: fix Rx queue stall on alloc failure When the system is under extreme memory pressure, page allocations can fail during the Rx buffer refill loop. If the number of buffers posted to hardware falls below a critical low threshold and the refill loop exits due to allocation failures, the queue can stall: 1. The device drops incoming packets because there are no descriptors. 2. Since no packets are processed, no Rx completions are generated. 3. Because no completions occur, NAPI is never scheduled, preventing the refill loop from running again even after memory is freed. This results in a permanent queue stall. Resolve this by introducing a starvation recovery timer for each Rx queue. If the number of buffers posted to hardware falls below a critical low threshold, start a timer to periodically reschedule NAPI. Once NAPI runs and successfully refills the queue above the threshold, the timer is not rescheduled. The threshold is set to 32 because a single maximum-sized Receive Segment Coalescing (RSC) packet can consume up to 19 descriptors in the Rx path. Lower thresholds (such as 8 or 16) would be insufficient to process a complete maximum-sized RSC packet, risking packet drops or unexpected hardware behavior under memory pressure. Setting the threshold to 32 guarantees a safe margin to handle at least one full RSC packet.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.18.42; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 <299d5728a7312fdd02059b074aebbe4ebbd391e4; 5.14; patch: 0; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 <0c317349b4baa5038d1fc373bf46d5a2419d1710; patch: 7.2-rc5; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 <689b9f588d2d7323dc66293fe594a68d030f400f; patch: 6.12.101; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 <91e0249f3ef62b75fe8c9c9372eaba32876e4b3a; patch: 7.1.6; patch: 6.6.151; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 <b65352a1bac64442ad95e64f385b40ccb9f1b0db
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.