CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc()

CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc()

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

qed: fix double free in qed_cxt_tables_alloc()

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.

Fix this by setting each CID bitmap pointer to NULL after bitmap_free()
to avoid double free.

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.

Runtime reproduction was not attempted because exercising the failing
allocation path requires device-specific setup.

The Linux kernel CVE team has assigned CVE-2026-64118 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 5.10.259 with commit 9fe030719bd083b766602692ee96c8c985798e3c
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 5.15.210 with commit 06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 6.1.175 with commit 8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 6.6.142 with commit 3904b993cc17ec5d7c5d3b57dbd0b775dafb9684
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 6.12.92 with commit bdf678a273cadbccc347f331ae2e93ff4d14834c
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 6.18.34 with commit 0e47fc1c9181ae029e0e35a865cbf2adcbae626c
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 7.0.11 with commit a04c207f0801abdd23a169b5f902a9845059a65a
	Issue introduced in 4.4 with commit fe56b9e6a8d957d6a20729d626027f800c17a2da and fixed in 7.1 with commit 2bccfb8476ca5f3548afbd623dc7a6980d4e77de

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-64118
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/ethernet/qlogic/qed/qed_cxt.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/9fe030719bd083b766602692ee96c8c985798e3c
	https://git.kernel.org/stable/c/06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227
	https://git.kernel.org/stable/c/8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb
	https://git.kernel.org/stable/c/3904b993cc17ec5d7c5d3b57dbd0b775dafb9684
	https://git.kernel.org/stable/c/bdf678a273cadbccc347f331ae2e93ff4d14834c
	https://git.kernel.org/stable/c/0e47fc1c9181ae029e0e35a865cbf2adcbae626c
	https://git.kernel.org/stable/c/a04c207f0801abdd23a169b5f902a9845059a65a
	https://git.kernel.org/stable/c/2bccfb8476ca5f3548afbd623dc7a6980d4e77de