Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68129gve: fix Rx queue stall on alloc failure

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68129, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.51% · top 56% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 9db46e19e5d6bdcd4bf811284a5b0df1b984ef80
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 42d525e751c61b876b2b0ae4e71ba7a8ab0c2777
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 299d5728a7312fdd02059b074aebbe4ebbd391e4
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 0c317349b4baa5038d1fc373bf46d5a2419d1710
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 91e0249f3ef62b75fe8c9c9372eaba32876e4b3a
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < 689b9f588d2d7323dc66293fe594a68d030f400f
    • affected 9b8dd5e5ea48bbb7532d20c4093a79d8283e4029 – < b65352a1bac64442ad95e64f385b40ccb9f1b0db
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68129 badge
[![CVE-2026-68129](https://cveledger.app/badge/CVE-2026-68129.svg)](https://cveledger.app/cve/CVE-2026-68129)

Record last updated .