<?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>Mon, 28 Sep 2026 07:46:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98028 — eth: nfp: drop the replaced rule from the list when reprogramming fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98028</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;eth: nfp: drop the replaced rule from the list when reprogramming fails&lt;/p&gt;
&lt;p&gt;nfp_net_fs_add() replaces an existing rule by deleting it from the
hardware, decrementing nn-&amp;gt;fs.count and programming the new one.  If
nfp_net_fs_add_hw() fails the old entry stays on nn-&amp;gt;fs.list - only the
success path reaches list_replace() - so the list is one longer than
nn-&amp;gt;fs.count, and it advertises a rule whose hardware entry has already
been torn down.&lt;/p&gt;
&lt;p&gt;nn-&amp;gt;fs.count is what ETHTOOL_GRXCLSRLCNT reports, so userspace then sizes
its buffer one entry short of what the GRXCLSRLALL walk wants to write.
That used to overwrite one u32 past the allocation; since the walk is
bounded it is a permanent -EMSGSIZE instead, as nothing ever resyncs the
counter.&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;eth: nfp: drop the replaced rule from the list when reprogramming fails&lt;/p&gt;
&lt;p&gt;nfp_net_fs_add() replaces an existing rule by deleting it from the
hardware, decrementing nn-&amp;gt;fs.count and programming the new one.  If
nfp_net_fs_add_hw() fails the old entry stays on nn-&amp;gt;fs.list - only the
success path reaches list_replace() - so the list is one longer than
nn-&amp;gt;fs.count, and it advertises a rule whose hardware entry has already
been torn down.&lt;/p&gt;
&lt;p&gt;nn-&amp;gt;fs.count is what ETHTOOL_GRXCLSRLCNT reports, so userspace then sizes
its buffer one entry short of what the GRXCLSRLALL walk wants to write.
That used to overwrite one u32 past the allocation; since the walk is
bounded it is a permanent -EMSGSIZE instead, as nothing ever resyncs the
counter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98028</guid>
    </item>
  </channel>
</rss>
