Unspecified impact via ignored SDMA initialization failure
Published Sep 17, 2026 · Updated Sep 18, 2026
Improper error handling in Linux allows local users to cause unspecified impact through hfi1 SDMA request processing. In set_txreq_header_ahg(), an sdma_txinit_ahg() failure leaves tx->txreq uninitialized, but the return value is ignored and processing continues as if initialization succeeded. Reaching the flaw requires local access, an active hfi1 RDMA device, and an initialization failure; published sources do not specify the resulting consequence.
Summary
What happened
Improper error handling in Linux allows local users to cause unspecified impact through hfi1 SDMA request processing. In set_txreq_header_ahg(), an sdma_txinit_ahg() failure leaves tx->txreq uninitialized, but the return value is ignored and processing continues as if initialization succeeded. Reaching the flaw requires local access, an active hfi1 RDMA device, and an initialization failure; published sources do not specify the resulting consequence.
The record
- CVE
- CVE-2026-93037
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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.14
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <091c6162c022cbdfb64219708a71728cfd1d4600
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <122a730675565ff2ad210537c3fc3afb8291d482
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <3416db552eb378e54cb2f2ce0db5f0df88654bda
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <5b7cefffd15d87c8103865f887cdcf9077d8094b
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <bf974994150cfd14bfc599748925f4d426e00d90
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <ca99431820e8cac19f6a091c04da54cbe8d64f52
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <cb73c2fe6e9cf563c99f22b7c8bca0d5f70d603e
- Affected versionversion=e3304b7cc4f14d365f46d6847a35563ae8b017f7 <fd6dee13f3857259b6b2ddd28e1ed95fd94ae2f9
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started