<?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://db.gcve.eu</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>Tue, 03 Nov 2026 08:14:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98561 — nfp: hold IPsec RX state under the XArray lock</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98561</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;nfp: hold IPsec RX state under the XArray lock&lt;/p&gt;
&lt;p&gt;nfp_net_ipsec_rx() drops the XArray lock before taking a reference to the
xfrm_state it found. The delete path can erase the entry and drop the last
state reference in that interval. RX can then try to increment a zero
refcount after the state has been queued for destruction.&lt;/p&gt;
&lt;p&gt;The driver queues firmware invalidation asynchronously; the delete path
does not wait for the command to complete or drain pending RX processing.&lt;/p&gt;
&lt;p&gt;The XFRM garbage collector waits for an RCU grace period before freeing
the state. That delays reclamation but does not make acquiring a reference
from zero valid.&lt;/p&gt;
&lt;p&gt;Take the xfrm_state reference before releasing the XArray lock so
xa_erase() cannot run between lookup and reference acquisition.&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;nfp: hold IPsec RX state under the XArray lock&lt;/p&gt;
&lt;p&gt;nfp_net_ipsec_rx() drops the XArray lock before taking a reference to the
xfrm_state it found. The delete path can erase the entry and drop the last
state reference in that interval. RX can then try to increment a zero
refcount after the state has been queued for destruction.&lt;/p&gt;
&lt;p&gt;The driver queues firmware invalidation asynchronously; the delete path
does not wait for the command to complete or drain pending RX processing.&lt;/p&gt;
&lt;p&gt;The XFRM garbage collector waits for an RCU grace period before freeing
the state. That delays reclamation but does not make acquiring a reference
from zero valid.&lt;/p&gt;
&lt;p&gt;Take the xfrm_state reference before releasing the XArray lock so
xa_erase() cannot run between lookup and reference acquisition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98561</guid>
    </item>
  </channel>
</rss>
