CVE-2026-64118
qed: fix double free in qed_cxt_tables_alloc()
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.
INFO
Published Date :
July 19, 2026, 4:17 p.m.
Last Modified :
July 19, 2026, 4:17 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64118
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Set CID bitmap pointers to NULL after freeing.
- Apply kernel patches to fix the double free vulnerability.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64118.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64118 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64118
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64118 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64118 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '9fe030719bd083b766602692ee96c8c985798e3c', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '3904b993cc17ec5d7c5d3b57dbd0b775dafb9684', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': 'bdf678a273cadbccc347f331ae2e93ff4d14834c', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '0e47fc1c9181ae029e0e35a865cbf2adcbae626c', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': 'a04c207f0801abdd23a169b5f902a9845059a65a', 'versionType': 'git'}, {'status': 'affected', 'version': 'fe56b9e6a8d957d6a20729d626027f800c17a2da', 'lessThan': '2bccfb8476ca5f3548afbd623dc7a6980d4e77de', 'versionType': 'git'}], 'programFiles': ['drivers/net/ethernet/qlogic/qed/qed_cxt.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.4'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.4', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.142', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.92', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/net/ethernet/qlogic/qed/qed_cxt.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227 Added Reference https://git.kernel.org/stable/c/0e47fc1c9181ae029e0e35a865cbf2adcbae626c Added Reference https://git.kernel.org/stable/c/2bccfb8476ca5f3548afbd623dc7a6980d4e77de Added Reference https://git.kernel.org/stable/c/3904b993cc17ec5d7c5d3b57dbd0b775dafb9684 Added Reference https://git.kernel.org/stable/c/8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb Added Reference https://git.kernel.org/stable/c/9fe030719bd083b766602692ee96c8c985798e3c Added Reference https://git.kernel.org/stable/c/a04c207f0801abdd23a169b5f902a9845059a65a Added Reference https://git.kernel.org/stable/c/bdf678a273cadbccc347f331ae2e93ff4d14834c