Kernel memory corruption via duplicate CID bitmap cleanup
Published Jul 19, 2026 · Updated Jul 19, 2026
Double-free in the Linux kernel QED driver in 4.4 through 7.1-rc3 allows attackers to corrupt kernel memory during device initialization. On a later PF or VF CID bitmap allocation failure, qed_cid_map_alloc() frees earlier bitmaps, after which qed_cxt_tables_alloc() calls qed_cxt_mngr_free() and frees them again. The path requires QED hardware and a failing bitmap allocation during driver resource setup; runtime reproduction has not been reported.
Summary
What happened
Double-free in the Linux kernel QED driver in 4.4 through 7.1-rc3 allows attackers to corrupt kernel memory during device initialization. On a later PF or VF CID bitmap allocation failure, qed_cid_map_alloc() frees earlier bitmaps, after which qed_cxt_tables_alloc() calls qed_cxt_mngr_free() and frees them again. The path requires QED hardware and a failing bitmap allocation during driver resource setup; runtime reproduction has not been reported.
The record
- CVE
- CVE-2026-64118
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <0e47fc1c9181ae029e0e35a865cbf2adcbae626c
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <2bccfb8476ca5f3548afbd623dc7a6980d4e77de
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <3904b993cc17ec5d7c5d3b57dbd0b775dafb9684
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <9fe030719bd083b766602692ee96c8c985798e3c
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <a04c207f0801abdd23a169b5f902a9845059a65a
- Affected versionversion=fe56b9e6a8d957d6a20729d626027f800c17a2da <bdf678a273cadbccc347f331ae2e93ff4d14834c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo