qed: fix double free in qed_cxt_tables_alloc()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.175, 6.6.142, 6.12.92, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux 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 Linux
4.4
- KernelLinux
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
References 8
git.kernel.org
- stable/c/9fe030719bd083b766602692ee96c8c985798e3c
- stable/c/06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227
- stable/c/8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb
- stable/c/3904b993cc17ec5d7c5d3b57dbd0b775dafb9684
- stable/c/bdf678a273cadbccc347f331ae2e93ff4d14834c
- stable/c/0e47fc1c9181ae029e0e35a865cbf2adcbae626c
- stable/c/a04c207f0801abdd23a169b5f902a9845059a65a
- stable/c/2bccfb8476ca5f3548afbd623dc7a6980d4e77de