gve: Fix stats report corruption on queue count change
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 24aeb56f2d38edf1b324bdb4f8bc6faf9f0f540c · < 11f8311f69e4c361717371b4901ff92daeb76e9c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gve: Fix stats report corruption on queue count change
The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC's stats.
When the number of queues is changed, the driver's stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting.
This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.
From the CVE record · Linux
The Linux kernel gve driver can allocate a stats region that is too small after the queue count increases, allowing the NIC to write past its end and corrupt memory. Decreasing the queue count can instead cause incorrect stats reporting. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the gve driver should check their installations; affected versions were not provided.