<?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 16:00:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64222 — octeontx2-pf: avoid double free of pool-&gt;stack on AQ init failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64222</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;octeontx2-pf: avoid double free of pool-&amp;gt;stack on AQ init failure&lt;/p&gt;
&lt;p&gt;otx2_pool_aq_init() frees pool-&amp;gt;stack when mailbox sync or retry
allocation fails, but leaves the pointer unchanged. Later,
otx2_sq_aura_pool_init() unwinds the partial setup through
otx2_aura_pool_free(), which frees pool-&amp;gt;stack again. The CN20K-specific
cn20k_pool_aq_init() implementation has the same bug in
its corresponding error path.&lt;/p&gt;
&lt;p&gt;Set pool-&amp;gt;stack to NULL immediately after the local free so the shared
cleanup path does not free the same stack again while cleaning up
partially initialized pool state.&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental analysis tool we are
developing for kernel memory-management bugs while analyzing
v6.13-rc1. The tool is still under development and is not yet publicly
available. Manual inspection confirms that the bug is still present in
v7.1-rc3.&lt;/p&gt;
&lt;p&gt;Runtime validation was not performed because reproducing this path
requires OcteonTX2/CN20K hardware.&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;octeontx2-pf: avoid double free of pool-&amp;gt;stack on AQ init failure&lt;/p&gt;
&lt;p&gt;otx2_pool_aq_init() frees pool-&amp;gt;stack when mailbox sync or retry
allocation fails, but leaves the pointer unchanged. Later,
otx2_sq_aura_pool_init() unwinds the partial setup through
otx2_aura_pool_free(), which frees pool-&amp;gt;stack again. The CN20K-specific
cn20k_pool_aq_init() implementation has the same bug in
its corresponding error path.&lt;/p&gt;
&lt;p&gt;Set pool-&amp;gt;stack to NULL immediately after the local free so the shared
cleanup path does not free the same stack again while cleaning up
partially initialized pool state.&lt;/p&gt;
&lt;p&gt;The bug was first flagged by an experimental analysis tool we are
developing for kernel memory-management bugs while analyzing
v6.13-rc1. The tool is still under development and is not yet publicly
available. Manual inspection confirms that the bug is still present in
v7.1-rc3.&lt;/p&gt;
&lt;p&gt;Runtime validation was not performed because reproducing this path
requires OcteonTX2/CN20K hardware.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64222</guid>
    </item>
  </channel>
</rss>
