<?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 14:56:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80843 — xfrm: fix xfrm_state_construct() auth-trunc leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80843</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: fix xfrm_state_construct() auth-trunc leak&lt;/p&gt;
&lt;p&gt;attach_auth_trunc() can allocate x-&amp;gt;aalg while leaving
x-&amp;gt;props.aalgo at zero when the selected auth algorithm has no
sadb_alg_id. One real case is cmac(aes).&lt;/p&gt;
&lt;p&gt;xfrm_state_construct() then treats !x-&amp;gt;props.aalgo as &amp;#34;no auth
algorithm attached yet&amp;#34; and calls attach_auth(). That overwrites
x-&amp;gt;aalg and loses the first allocation. Any later failure or teardown
only frees the replacement pointer.&lt;/p&gt;
&lt;p&gt;Check whether x-&amp;gt;aalg is already attached instead of inferring that
state from x-&amp;gt;props.aalgo.&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: fix xfrm_state_construct() auth-trunc leak&lt;/p&gt;
&lt;p&gt;attach_auth_trunc() can allocate x-&amp;gt;aalg while leaving
x-&amp;gt;props.aalgo at zero when the selected auth algorithm has no
sadb_alg_id. One real case is cmac(aes).&lt;/p&gt;
&lt;p&gt;xfrm_state_construct() then treats !x-&amp;gt;props.aalgo as &amp;#34;no auth
algorithm attached yet&amp;#34; and calls attach_auth(). That overwrites
x-&amp;gt;aalg and loses the first allocation. Any later failure or teardown
only frees the replacement pointer.&lt;/p&gt;
&lt;p&gt;Check whether x-&amp;gt;aalg is already attached instead of inferring that
state from x-&amp;gt;props.aalgo.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80843</guid>
    </item>
  </channel>
</rss>
