<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 14:43:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68795 — ethtool: Avoid overflowing userspace buffer on stats query</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68795</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: Avoid overflowing userspace buffer on stats query&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;If the number of stats changes between these calls (e.g., due to device
reconfiguration), userspace&amp;#39;s buffer allocation will be incorrect,
potentially leading to buffer overflow.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Some drivers try to handle this internally:
- bnad_get_ethtool_stats() returns early in case stats.n_stats is not
  equal to the driver&amp;#39;s stats count.
- micrel/ksz884x also makes sure not to write anything beyond
  stats.n_stats and overflow the buffer.&lt;/p&gt;
&lt;p&gt;However, both use stats.n_stats which is already assigned with the value
returned from get_sset_count(), hence won&amp;#39;t solve the issue described
here.&lt;/p&gt;
&lt;p&gt;Change ethtool_get_strings(), ethtool_get_stats(),
ethtool_get_phy_stats() to not return anything in case of a mismatch
between userspace&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: Avoid overflowing userspace buffer on stats query&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;If the number of stats changes between these calls (e.g., due to device
reconfiguration), userspace&amp;#39;s buffer allocation will be incorrect,
potentially leading to buffer overflow.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Some drivers try to handle this internally:
- bnad_get_ethtool_stats() returns early in case stats.n_stats is not
  equal to the driver&amp;#39;s stats count.
- micrel/ksz884x also makes sure not to write anything beyond
  stats.n_stats and overflow the buffer.&lt;/p&gt;
&lt;p&gt;However, both use stats.n_stats which is already assigned with the value
returned from get_sset_count(), hence won&amp;#39;t solve the issue described
here.&lt;/p&gt;
&lt;p&gt;Change ethtool_get_strings(), ethtool_get_stats(),
ethtool_get_phy_stats() to not return anything in case of a mismatch
between userspace&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68795</guid>
    </item>
  </channel>
</rss>
