CVE-2025-38735: gve: prevent ethtool ops after shutdown
In the Linux kernel, the following vulnerability has been resolved:
gve: prevent ethtool ops after shutdown
A crash can occur if an ethtool operation is invoked
after shutdown() is called.
shutdown() is invoked during system shutdown to stop DMA operations
without performing expensive deallocations. It is discouraged to
unregister the netdev in this path, so the device may still be visible
to userspace and kernel helpers.
In gve, shutdown() tears down most internal data structures. If an
ethtool operation is dispatched after shutdown(), it will dereference
freed or NULL pointers, leading to a kernel panic. While graceful
shutdown normally quiesces userspace before invoking the reboot
syscall, forced shutdowns (as observed on GCP VMs) can still trigger
this path.
Fix by calling netif_device_detach() in shutdown().
This marks the device as detached so the ethtool ioctl handler
will skip dispatching operations to the driver.
Security readout for executives and security teams
Plain-English summary
A shutdown race in the Linux gve network driver can crash the operating system. During forced shutdown, the device may remain visible after internal data is removed; a concurrent ethtool request can then trigger a kernel panic. The principal business impact is disrupted shutdown or restart of affected systems, particularly GCP virtual machines using gve.
Executive priority
Treat as a high-priority reliability issue for affected GCP or gve-based fleets, especially systems frequently stopped, restarted, or preempted. Patch through normal expedited kernel maintenance. Broader emergency action is not supported because exposure is conditional and the supplied sources show no active exploitation.
Technical view
The gve shutdown handler releases or clears internal structures while leaving the network device accessible. A subsequent ethtool operation can dereference freed or NULL pointers and panic the kernel. The fix calls netif_device_detach() during shutdown, causing the ethtool ioctl handler to avoid dispatching operations to the detached driver.
Likely exposure
Exposure requires Linux using the gve network driver, an affected kernel build, and an ethtool operation racing with shutdown. Forced shutdowns on GCP VMs are specifically reported as capable of reaching this path. The bundled version data is ambiguous, so validate exact exposure using kernel or distribution guidance.
Exploitation context
The CVSS 3.1 score is 7.8 and describes local, low-complexity access with low privileges and no user interaction. However, the documented outcome is a kernel panic during shutdown. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation.
Researcher notes
This is a shutdown-time lifetime-management flaw involving an accessible netdev after gve teardown. The source describes freed or NULL pointer dereferences but does not establish practical confidentiality or integrity impact beyond the CVSS vector. Exact vulnerable release boundaries cannot be reliably reconstructed from the flattened version list; assess vendor backports by package and commit provenance.
Mitigation direction
Update to a vendor-supported kernel containing the referenced gve shutdown fix.
Check Linux distribution and cloud-provider advisories for applicable fixed package versions.
Prioritize affected GCP workloads where forced shutdowns or automated lifecycle operations occur.
Limit unnecessary local access capable of invoking network-device management operations until updated.
Validation and detection
Confirm whether each system uses the gve network driver and corresponding virtual network device.
Compare the installed kernel package with current distribution or vendor guidance for CVE-2025-38735.
Verify the deployed kernel incorporates netif_device_detach() in the gve shutdown path or an equivalent backport.
Review shutdown and serial-console logs for gve-related kernel panics around forced restarts.
Test shutdown behavior only in an isolated, non-production environment after applying the update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38735 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.