Vulnerability · Published Jan 13, 2026 · Assigned by Linux

CVE-2025-68795ethtool: Avoid overflowing userspace buffer on stats query

High 7.8

In plain English

A high-severity heap buffer overflow in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 93.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: ethtool: Avoid overflowing userspace buffer on stats query The ethtool -S command operates across three ioctl calls: ETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and ETHTOOL_GSTATS for the values. If the number of stats changes between these calls (e.g., due to device reconfiguration), userspace's buffer allocation will be incorrect, potentially leading to buffer overflow. Drivers are generally expected to maintain stable stat counts, but some drivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making this scenario possible. Some drivers try to handle this internally: - bnad_get_ethtool_stats() returns early in case stats.n_stats is not equal to the driver's stats count. - micrel/ksz884x also makes sure not to write anything beyond stats.n_stats and overflow the buffer. However, both use stats.n_stats which is already assigned with the value returned from get_sset_count(), hence won't solve the issue described here. Change ethtool_get_strings(), ethtool_get_stats(), ethtool_get_phy_stats() to not return anything in case of a mismatch between userspace's size and get_sset_size(), to prevent buffer overflow. The returned n_stats value will be equal to zero, to reflect that nothing has been returned. This could result in one of two cases when using upstream ethtool, depending on when the size change is detected: 1. When detected in ethtool_get_strings(): # ethtool -S eth2 no stats available 2. When detected in get stats, all stats will be reported as zero. Both cases are presumably transient, and a subsequent ethtool call should succeed. Other than the overflow avoidance, these two cases are very evident (no output/cleared stats), which is arguably better than presenting incorrect/shifted stats. I also considered returning an error instead of a "silent" response, but that seems more destructive towards userspace apps. Notes: - This patch does not claim to fix the inherent race, it only makes sure that we do not overflow the userspace buffer, and makes for a more predictable behavior. - RTNL lock is held during each ioctl, the race window exists between the separate ioctl calls when the lock is released. - Userspace ethtool always fills stats.n_stats, but it is likely that these stats ioctls are implemented in other userspace applications which might not fill it. The added code checks that it's not zero, to prevent any regressions.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.162-1DEBIAN-CVE-2025-68795
Debian:13linux6.12.69-1DSA-6126-1
Debian:13linux6.12.69-1DEBIAN-CVE-2025-68795
Debian:14linux6.18.3-1DEBIAN-CVE-2025-68795
Ubuntu:22.04:LTSlinux5.15.0-173.183UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux6.8.0-110.110UBUNTU-CVE-2025-68795
Ubuntu:25.10linux6.17.0-22.22UBUNTU-CVE-2025-68795
Ubuntu:25.10linux6.17.0-22.22USN-8177-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-aws6.8.0-1052.55UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-aws6.17.0-1012.12UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-aws6.17.0-1012.12USN-8183-2
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure6.8.0-1054.60UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-azure6.17.0-1013.13UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-azure6.17.0-1013.13USN-8245-1
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1USN-8245-1
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gcp6.8.0-1054.57UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-gcp6.17.0-1012.12USN-8183-1
Ubuntu:25.10linux-gcp6.17.0-1012.12UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1USN-8183-1
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gke5.15.0-1099.105UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gke6.8.0-1050.56UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1086.94UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1037.40UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-ibm5.15.0-1097.100UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-ibm6.8.0-1051.51UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1098.104UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-kvm5.15.0-1095.100UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-110.110.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1098.99UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1051.54UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1051.54.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1055.55UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1022.22UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1044.44UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20USN-8245-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oracle5.15.0-1100.106UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oracle6.8.0-1049.50UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-oracle6.17.0-1011.11USN-8183-2
Ubuntu:25.10linux-oracle6.17.0-1011.11UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1USN-8183-2
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-raspi6.8.0-1052.56UBUNTU-CVE-2025-68795
Ubuntu:25.10linux-raspi6.17.0-1013.13UBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68795
Ubuntu:25.10linux-realtime6.17.0-1010.11USN-8177-1
Ubuntu:25.10linux-realtime6.17.0-1010.11UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68795
Ubuntu:25.10linux-riscv6.17.0-22.22.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-22.22.1~24.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68795
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-68795
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1067.71UBUNTU-CVE-2025-68795

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 3df375a1e75483b7d973c3cc2e46aa374db8428b1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before f9dc0f45d2cd0189ce666288a29d2cc32c2e44d51da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 4afcb985355210e1688560dc47e64b94dad35d711da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before ca9983bc3a1189bd72f9ae449d925a66b26163261da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 7bea09f60f2ad5d232e2db8f1c14e850fd3fd4161da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 4066b5b546293f44cd6d0e84ece6e3ee7ff270931da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 7b07be1ff1cb6c49869910518650e8d0abc7d25f
Linux Linux 2.6.12

Weakness: CWE-122 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References