| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025090543-CVE-2025-38735-3fae@gregkh> Date: Fri, 5 Sep 2025 19:20:44 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38735: gve: prevent ethtool ops after shutdown From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== 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. The Linux kernel CVE team has assigned CVE-2025-38735 to this issue. Affected and fixed versions =========================== Issue introduced in 5.17 with commit 974365e518617c9ce917f61aacbba07e4bedcca0 and fixed in 6.1.149 with commit 48a4e89d50e8ea52e800bc7865970b92fcf4647c Issue introduced in 5.17 with commit 974365e518617c9ce917f61aacbba07e4bedcca0 and fixed in 6.6.103 with commit ba51d73408edf815cbaeab148625576c2dd90192 Issue introduced in 5.17 with commit 974365e518617c9ce917f61aacbba07e4bedcca0 and fixed in 6.12.44 with commit a7efffeecb881b4649fdc30de020ef910f35d646 Issue introduced in 5.17 with commit 974365e518617c9ce917f61aacbba07e4bedcca0 and fixed in 6.16.4 with commit 9d8a41e9a4ff83ff666de811e7f012167cdc00e9 Issue introduced in 5.17 with commit 974365e518617c9ce917f61aacbba07e4bedcca0 and fixed in 6.17-rc3 with commit 75a9a46d67f46d608205888f9b34e315c1786345 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-38735 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/ethernet/google/gve/gve_main.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/48a4e89d50e8ea52e800bc7865970b92fcf4647c https://git.kernel.org/stable/c/ba51d73408edf815cbaeab148625576c2dd90192 https://git.kernel.org/stable/c/a7efffeecb881b4649fdc30de020ef910f35d646 https://git.kernel.org/stable/c/9d8a41e9a4ff83ff666de811e7f012167cdc00e9 https://git.kernel.org/stable/c/75a9a46d67f46d608205888f9b34e315c1786345
Powered by blists - more mailing lists