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… (CVE-2026-64118)
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.
AI Analysis
Technical Summary
The Linux kernel's qed driver contained a double free vulnerability in the qed_cxt_tables_alloc() function. When allocation of PF or VF CID bitmaps fails, the error handling code frees previously allocated bitmaps and then calls qed_cxt_mngr_free(), which attempts to free the same bitmaps again, causing a double free. The patch sets each CID bitmap pointer to NULL after freeing to prevent this. The vulnerability was found via an experimental kernel memory-management analysis tool and confirmed in kernel version 7.1-rc3. No runtime reproduction or exploitation has been observed due to the complexity of triggering the failure path.
Potential Impact
Double free vulnerabilities can lead to memory corruption, which may cause kernel crashes or potentially enable escalation of privileges or arbitrary code execution. However, no known exploits are reported for this issue, and reproducing the failure requires specific device configurations, limiting practical impact at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch or fix link is provided, users should monitor Linux kernel updates for a fix addressing this double free in the qed driver. Until then, avoid configurations that might trigger the failing allocation path if possible.
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… (CVE-2026-64118)
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.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's qed driver contained a double free vulnerability in the qed_cxt_tables_alloc() function. When allocation of PF or VF CID bitmaps fails, the error handling code frees previously allocated bitmaps and then calls qed_cxt_mngr_free(), which attempts to free the same bitmaps again, causing a double free. The patch sets each CID bitmap pointer to NULL after freeing to prevent this. The vulnerability was found via an experimental kernel memory-management analysis tool and confirmed in kernel version 7.1-rc3. No runtime reproduction or exploitation has been observed due to the complexity of triggering the failure path.
Potential Impact
Double free vulnerabilities can lead to memory corruption, which may cause kernel crashes or potentially enable escalation of privileges or arbitrary code execution. However, no known exploits are reported for this issue, and reproducing the failure requires specific device configurations, limiting practical impact at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch or fix link is provided, users should monitor Linux kernel updates for a fix addressing this double free in the qed driver. Until then, avoid configurations that might trigger the failing allocation path if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wf22-p86j-w6w4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64118"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912a8b2
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:43:18 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.