CyberSecBulletin
CVE-2026-68129NVD status: Received

Linux: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2026-68129 is a high-severity uncontrolled resource consumption vulnerability in Linux, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80, 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777, 299d5728a7312fdd02059b074aebbe4ebbd391e4 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80 or 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777 or 299d5728a7312fdd02059b074aebbe4ebbd391e4 or 0c317349b4baa5038d1fc373bf46d5a2419d1710, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 299d5728a7312fdd02059b074aebbe4ebbd391e4; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 0c317349b4baa5038d1fc373bf46d5a2419d1710; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 91e0249f3ef62b75fe8c9c9372eaba32876e4b3a; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, 689b9f588d2d7323dc66293fe594a68d030f400f; 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 up to, but not including, b65352a1bac64442ad95e64f385b40ccb9f1b0db; 5.149db46e19e5d6bdcd4bf811284a5b0df1b984ef80, 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777, 299d5728a7312fdd02059b074aebbe4ebbd391e4, 0c317349b4baa5038d1fc373bf46d5a2419d1710, 91e0249f3ef62b75fe8c9c9372eaba32876e4b3a, 689b9f588d2d7323dc66293fe594a68d030f400f

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA.

Official description

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: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.