CVE-2026-64118High· 8.4▾ TwilightIn 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 previ…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 46.2 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
Last analysed / modified upstream
0.2% → 0.2%
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.
Linux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 9fe030719bd083b766602692ee96c8c985798e3cLinux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227Linux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 8cf5e4d2ca6b101d163c7423a426fb0aec34f7bbLinux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 3904b993cc17ec5d7c5d3b57dbd0b775dafb9684Linux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < bdf678a273cadbccc347f331ae2e93ff4d14834cLinux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 0e47fc1c9181ae029e0e35a865cbf2adcbae626cLinux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < a04c207f0801abdd23a169b5f902a9845059a65aLinux >= fe56b9e6a8d957d6a20729d626027f800c17a2da < 2bccfb8476ca5f3548afbd623dc7a6980d4e77deLinux 4.4Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets