Service degradation via qedi DMA memory leak
Published Dec 29, 2024 · Updated May 11, 2026
Memory leak in the Linux kernel qedi SCSI driver from 4.10 allows local users to degrade service by exhausting DMA memory. When qedi_alloc_and_init_sb allocates the sb_virt DMA buffer and qed_sb_init then fails, the error path returns without calling dma_free_coherent. Reachability requires the qedi driver and a status-block initialization failure; repeated failures consume unreleased DMA memory and affect availability without reported data disclosure or modification.
Summary
What happened
Memory leak in the Linux kernel qedi SCSI driver from 4.10 allows local users to degrade service by exhausting DMA memory. When qedi_alloc_and_init_sb allocates the sb_virt DMA buffer and qed_sb_init then fails, the error path returns without calling dma_free_coherent. Reachability requires the qedi driver and a status-block initialization failure; repeated failures consume unreleased DMA memory and affect availability without reported data disclosure or modification.
The record
- CVE
- CVE-2024-56747
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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.10
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <10a6fc486ac40a410f0fb84cc15161238eccd20a
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <20b775cf274cfbfa3da871a1108877e17b8b19e1
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <4e48e5b26b3edc0e1dd329201ffc924a7a1f9337
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <95bbdca4999bc59a72ebab01663d421d6ce5775d
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <a4d2011cbe039b25024831427b60ab91ee247066
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <b778b5240485106abf665eb509cc01779ed0cb00
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <bb8b45883eb072adba297922b67d1467082ac880
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <cfc76acaf2c4b43d1e140f1e4cbde15adb540bc5
- Affected versionversion=ace7f46ba5fde7273207c7122b0650ceb72510e0 <eaf92fad1f21be63427920c12f22227e5f757424
What conditions does exploitation require?
What is affected?
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