<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T20:59:02.440076+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-80843</id>
    <title>CVE-2026-80843 — xfrm: fix xfrm_state_construct() auth-trunc leak</title>
    <updated>2026-10-04T20:59:02.442502+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>xfrm: fix xfrm_state_construct() auth-trunc leak</p>
<p>attach_auth_trunc() can allocate x-&gt;aalg while leaving
x-&gt;props.aalgo at zero when the selected auth algorithm has no
sadb_alg_id. One real case is cmac(aes).</p>
<p>xfrm_state_construct() then treats !x-&gt;props.aalgo as "no auth
algorithm attached yet" and calls attach_auth(). That overwrites
x-&gt;aalg and loses the first allocation. Any later failure or teardown
only frees the replacement pointer.</p>
<p>Check whether x-&gt;aalg is already attached instead of inferring that
state from x-&gt;props.aalgo.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80843"/>
  </entry>
</feed>
