CVE-2026-68129gve: fix Rx queue stall on alloc failure
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80; from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777; from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before 299d5728a7312fdd02059b074aebbe4ebbd391e4; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 builds before 0c317349b4baa5038d1fc373bf46d5a2419d1710; from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before 91e0249f3ef62b75fe8c9c9372eaba32876e4b3a; from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before 689b9f588d2d7323dc66293fe594a68d030f400f; from 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 before b65352a1bac64442ad95e64f385b40ccb9f1b0db | CNA record |
References
- https://git.kernel.org/stable/c/9db46e19e5d6bdcd4bf811284a5b0df1b984ef80
- https://git.kernel.org/stable/c/42d525e751c61b876b2b0ae4e71ba7a8ab0c2777
- https://git.kernel.org/stable/c/299d5728a7312fdd02059b074aebbe4ebbd391e4
- https://git.kernel.org/stable/c/0c317349b4baa5038d1fc373bf46d5a2419d1710
- https://git.kernel.org/stable/c/91e0249f3ef62b75fe8c9c9372eaba32876e4b3a
- https://git.kernel.org/stable/c/689b9f588d2d7323dc66293fe594a68d030f400f
- https://git.kernel.org/stable/c/b65352a1bac64442ad95e64f385b40ccb9f1b0db
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.