Service interruption via leaked DMA allocations
Published Apr 17, 2024 · Updated May 11, 2026
A memory leak in the Linux kernel hfi1 driver allows local users to cause a service interrupt when device initialization fails. If dma_alloc_coherent fails for a credit-return array entry, init_credit_return exits without freeing dd->cr_base or entries allocated earlier. The path requires Intel Omni-Path hardware and an allocation failure; retained coherent DMA buffers can exhaust kernel memory and interrupt the host.
Summary
What happened
A memory leak in the Linux kernel hfi1 driver allows local users to cause a service interrupt when device initialization fails. If dma_alloc_coherent fails for a credit-return array entry, init_credit_return exits without freeing dd->cr_base or entries allocated earlier. The path requires Intel Omni-Path hardware and an allocation failure; retained coherent DMA buffers can exhaust kernel memory and interrupt the host.
The record
- CVE
- CVE-2024-26839
- Published
- Apr 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 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.3
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <2e4f9f20b32658ef3724aa46f7aef4908d2609e3
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <3fa240bb6b2dbb3e7a3ee1440a4889cbb6207eb7
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <52de5805c147137205662af89ed7e083d656ae25
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <809aa64ebff51eb170ee31a95f83b2d21efa32e2
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <8412c86e89cc78d8b513cb25cf2157a2adf3670a
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <b41d0ade0398007fb746213f09903d52a920e896
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <cecfb90cf71d91e9efebd68b9e9b84661b277cc8
- Affected versionversion=7724105686e718ac476a6ad3304fea2fbcfcffde <f0d857ce31a6bc7a82afcdbadb8f7417d482604b
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