<?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-01T16:06:53.726053+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-23344</id>
    <title>CVE-2026-23344 — crypto: ccp - Fix use-after-free on error path</title>
    <updated>2026-10-01T16:06:53.730133+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>crypto: ccp - Fix use-after-free on error path</p>
<p>In the error path of sev_tsm_init_locked(), the code dereferences 't'
after it has been freed with kfree(). The pr_err() statement attempts
to access t-&gt;tio_en and t-&gt;tio_init_done after the memory has been
released.</p>
<p>Move the pr_err() call before kfree(t) to access the fields while the
memory is still valid.</p>
<p>This issue reported by Smatch static analyser</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-23344"/>
  </entry>
</feed>
