<?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>Tue, 29 Sep 2026 21:41:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80845 — xfrm: avoid lock inversion in nat keepalive work</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80845</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;xfrm: avoid lock inversion in nat keepalive work&lt;/p&gt;
&lt;p&gt;nat_keepalive_work() walks the state table while xfrm_state_walk()
holds net-&amp;gt;xfrm.xfrm_state_lock. Its callback then acquires x-&amp;gt;lock,
which conflicts with the delete path taking the same locks in reverse
order via xfrm_state_delete() and __xfrm_state_delete(). This creates
an AB-BA deadlock that is reported by lockdep when a NAT keepalive
worker races with SA deletion.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the keepalive walk into two phases. First,
collect the candidate states while the walk holds xfrm_state_lock and
take a reference on each state. Then, after the walk completes, process
each collected state and acquire x-&amp;gt;lock without nesting it under
xfrm_state_lock.&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;xfrm: avoid lock inversion in nat keepalive work&lt;/p&gt;
&lt;p&gt;nat_keepalive_work() walks the state table while xfrm_state_walk()
holds net-&amp;gt;xfrm.xfrm_state_lock. Its callback then acquires x-&amp;gt;lock,
which conflicts with the delete path taking the same locks in reverse
order via xfrm_state_delete() and __xfrm_state_delete(). This creates
an AB-BA deadlock that is reported by lockdep when a NAT keepalive
worker races with SA deletion.&lt;/p&gt;
&lt;p&gt;Fix this by splitting the keepalive walk into two phases. First,
collect the candidate states while the walk holds xfrm_state_lock and
take a reference on each state. Then, after the walk completes, process
each collected state and acquire x-&amp;gt;lock without nesting it under
xfrm_state_lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80845</guid>
    </item>
  </channel>
</rss>
