Live › vulnerability › CVE-2026-99048
Go to dashboardThe gve Google Virtual NIC driver calls unlocked NAPI disable and enable functions while the netdev lock is already held, so disabling XSK pools deadlocks the thread. The impact described is a hang or denial of service on affected systems, not code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the gve driver (Google Compute Engine virtual NICs) that use AF_XDP XSK pools and disable them while queue management ops are in use. The sources do not give affected kernel version ranges. Hosts without the gve driver or without XSK pool use are unlikely to be affected.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
gve: fix napi_disable deadlock when attempting to disable XSK pools
When disabling XSK pools, GVE calls the unlocked versions of napi_disable and napi_enable. However, the netdev lock has already been acquired before ndo_bpf is called because GVE supports queue management ops. Calling the unlocked versions of napi_disable/enable results in a deadlock when attempting to disable XSK pools, as the thread attempts to re-acquire a lock it already holds.
Update the NAPI calls to use the locked versions.
This issue was found in production.
This page as .md · .json · in your agent: get_signal("CVE-2026-99048")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.