<?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-09-30T03:51:31.961544+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-31471</id>
    <title>CVE-2026-31471 — xfrm: iptfs: only publish mode_data after clone setup</title>
    <updated>2026-09-30T03:51:31.975853+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: iptfs: only publish mode_data after clone setup</p>
<p>iptfs_clone_state() stores x-&gt;mode_data before allocating the reorder
window. If that allocation fails, the code frees the cloned state and
returns -ENOMEM, leaving x-&gt;mode_data pointing at freed memory.</p>
<p>The xfrm clone unwind later runs destroy_state() through x-&gt;mode_data,
so the failed clone path tears down IPTFS state that clone_state()
already freed.</p>
<p>Keep the cloned IPTFS state private until all allocations succeed so
failed clones leave x-&gt;mode_data unset. The destroy path already
handles a NULL mode_data pointer.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31471"/>
  </entry>
</feed>
