<?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>Sun, 04 Oct 2026 13:49:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47556 — ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2021-47556</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: ioctl: fix potential NULL deref in ethtool_set_coalesce()&lt;/p&gt;
&lt;p&gt;ethtool_set_coalesce() now uses both the .get_coalesce() and
.set_coalesce() callbacks. But the check for their availability is
buggy, so changing the coalesce settings on a device where the driver
provides only _one_ of the callbacks results in a NULL pointer
dereference instead of an -EOPNOTSUPP.&lt;/p&gt;
&lt;p&gt;Fix the condition so that the availability of both callbacks is
ensured. This also matches the netlink code.&lt;/p&gt;
&lt;p&gt;Note that reproducing this requires some effort - it only affects the
legacy ioctl path, and needs a specific combination of driver options:
- have .get_coalesce() and .coalesce_supported but no
 .set_coalesce(), or
- have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t
  cause the crash as it first attempts to call ethtool_get_coalesce()
  and bails out on error.&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: ioctl: fix potential NULL deref in ethtool_set_coalesce()&lt;/p&gt;
&lt;p&gt;ethtool_set_coalesce() now uses both the .get_coalesce() and
.set_coalesce() callbacks. But the check for their availability is
buggy, so changing the coalesce settings on a device where the driver
provides only _one_ of the callbacks results in a NULL pointer
dereference instead of an -EOPNOTSUPP.&lt;/p&gt;
&lt;p&gt;Fix the condition so that the availability of both callbacks is
ensured. This also matches the netlink code.&lt;/p&gt;
&lt;p&gt;Note that reproducing this requires some effort - it only affects the
legacy ioctl path, and needs a specific combination of driver options:
- have .get_coalesce() and .coalesce_supported but no
 .set_coalesce(), or
- have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn&amp;#39;t
  cause the crash as it first attempts to call ethtool_get_coalesce()
  and bails out on error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2021-47556</guid>
    </item>
  </channel>
</rss>
