CVE-2026-23386gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL
- 5.5MediumCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL In DQ-QPL mode, gve_tx_clean_pending_packets() incorrectly uses the RDA buffer cleanup path. It iterates num_bufs times and attempts to unmap entries in the dma array. This leads to two issues: 1. The dma array shares storage with tx_qpl_buf_ids (union). Interpreting buffer IDs as DMA addresses results in attempting to unmap incorrect memory locations. 2. num_bufs in QPL mode (counting 2K chunks) can significantly exceed the size of the dma array, causing out-of-bounds access warnings (trace below is how we noticed this issue). UBSAN: array-index-out-of-bounds in drivers/net/ethernet/drivers/net/ethernet/google/gve/gve_tx_dqo.c:178:5 index 18 is out of range for type 'dma_addr_t[18]' (aka 'unsigned long long[18]') Workqueue: gve gve_service_task [gve] Call Trace: <TASK> dump_stack_lvl+0x33/0xa0 __ubsan_handle_out_of_bounds+0xdc/0x110 gve_tx_stop_ring_dqo+0x182/0x200 [gve] gve_close+0x1be/0x450 [gve] gve_reset+0x99/0x120 [gve] gve_service_task+0x61/0x100 [gve] process_scheduled_works+0x1e9/0x380 Fix this by properly checking for QPL mode and delegating to gve_free_tx_qpl_bufs() to reclaim the buffers.
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 8 months later
· 8 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a6fb8d5a8b6925f1e635818d3dd2d89531d4a058 – < 71511dae56a75ce161aa746741e5c498feaea393
- affected a6fb8d5a8b6925f1e635818d3dd2d89531d4a058 – < c171f90f58974c784db25e0606051541cb71b7f0
- affected a6fb8d5a8b6925f1e635818d3dd2d89531d4a058 – < 07e0c80e17ef781799e7cd5c41a7bf44f1bf6a5f
- affected a6fb8d5a8b6925f1e635818d3dd2d89531d4a058 – < 3744ebd8ffaa542ae8110fb449adcac0202f4cc8
- affected a6fb8d5a8b6925f1e635818d3dd2d89531d4a058 – < fb868db5f4bccd7a78219313ab2917429f715cea
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.17 – ≤ 6.18.*
- unaffected 6.19.7 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/71511dae56a75ce161aa746741e5c498feaea393 (opens in a new tab)
- https://git.kernel.org/stable/c/c171f90f58974c784db25e0606051541cb71b7f0 (opens in a new tab)
- https://git.kernel.org/stable/c/07e0c80e17ef781799e7cd5c41a7bf44f1bf6a5f (opens in a new tab)
- https://git.kernel.org/stable/c/3744ebd8ffaa542ae8110fb449adcac0202f4cc8 (opens in a new tab)
- https://git.kernel.org/stable/c/fb868db5f4bccd7a78219313ab2917429f715cea (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-15384 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23386)Record last updated .