CVE-2026-23386 Details
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.
A vulnerability exists in the Linux kernel's Google GVE driver, specifically in the buffer cleanup process for QPL mode. The issue arises in the 'gve_tx_clean_pending_packets' function, which improperly handles buffer deallocation by using the RDA buffer cleanup method. This mismanagement leads to two main problems: first, the DMA array, which is used to store buffer IDs, is misinterpreted when QPL mode is active, causing incorrect memory locations to be unmapped. Second, the 'num_bufs' count in QPL mode can greatly exceed the actual size of the DMA array, resulting in out-of-bounds access errors. These issues were identified through warnings generated by the Undefined Behavior Sanitizer (UBSAN), indicating array index violations.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/07e0c80e17ef781799e7cd5c41a7bf44f1bf6a5f | kernel.org | Patch |
| https://git.kernel.org/stable/c/3744ebd8ffaa542ae8110fb449adcac0202f4cc8 | kernel.org | Patch |
| https://git.kernel.org/stable/c/71511dae56a75ce161aa746741e5c498feaea393 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c171f90f58974c784db25e0606051541cb71b7f0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/fb868db5f4bccd7a78219313ab2917429f715cea | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6.1, < 6.6.130 >= 6.7, < 6.12.78 >= 6.13, < 6.18.17 >= 6.19, < 6.19.7 6.6 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Mar 25, 2026 | New CVE Received | kernel.org |