CVE-2026-68129High· 7.5▾ TwilightIn 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…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.5%
Last analysed / modified upstream
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:
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.
Linux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80Linux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777Linux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 299d5728a7312fdd02059b074aebbe4ebbd391e4Linux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 0c317349b4baa5038d1fc373bf46d5a2419d1710Linux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 91e0249f3ef62b75fe8c9c9372eaba32876e4b3aLinux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < 689b9f588d2d7323dc66293fe594a68d030f400fLinux >= 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 < b65352a1bac64442ad95e64f385b40ccb9f1b0dbLinux 5.14Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets