VDB

CVE-2026-68129

CVE-2026-68129 PUBLISHED CVSS 7.5 HIGH

gve: fix Rx queue stall on alloc failure

Reported by linux · Published August 10, 2026

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxb65352a1bac64442ad95e64f385b40ccb9f1b0db, 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80, 91e0249f3ef62b75fe8c9c9372eaba32876e4b3a, 689b9f588d2d7323dc66293fe594a68d030f400f, 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777, 299d5728a7312fdd02059b074aebbe4ebbd391e4, 0c317349b4baa5038d1fc373bf46d5a2419d1710

Risk scores

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

Affected products

VendorProductVersions
LinuxLinux9b8dd5e5ea48bbb7532d20c4093a79d8283e4029, 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029, 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029
LinuxLinux5.14, 0, 5.15.216
LinuxLinux6.1.183, 6.12.101, 6.18.42
linuxlinux_kernel5.14, 5.14, 5.14

Timeline

  • Aug 10, 2026 CVE Published
  • Aug 11, 2026 Coalition ESS Score
  • Aug 16, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (30 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-68129
vulnetix vdb fixes CVE-2026-68129

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68129/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›