https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:04:49 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64118 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>qed: fix double free in qed_cxt_tables_alloc()</p> <p>If one of the later PF or VF CID bitmap allocations fails, qed_cid_map_alloc() jumps to cid_map_fail and frees the previously allocated CID bitmaps before returning an error. qed_cxt_tables_alloc() then calls qed_cxt_mngr_free(), which invokes qed_cid_map_free() again.</p> <p>Fix this by setting each CID bitmap pointer to NULL after bitmap_free() to avoid double free.</p> <p>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.</p> <p>Runtime reproduction was not attempted because exercising the failing allocation path requires device-specific setup.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>qed: fix double free in qed_cxt_tables_alloc()</p> <p>If one of the later PF or VF CID bitmap allocations fails, qed_cid_map_alloc() jumps to cid_map_fail and frees the previously allocated CID bitmaps before returning an error. qed_cxt_tables_alloc() then calls qed_cxt_mngr_free(), which invokes qed_cid_map_free() again.</p> <p>Fix this by setting each CID bitmap pointer to NULL after bitmap_free() to avoid double free.</p> <p>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.</p> <p>Runtime reproduction was not attempted because exercising the failing allocation path requires device-specific setup.</p> https://vulnerability.circl.lu/vuln/cve-2026-64118