Service interruption via unchecked DMA-pool creation failure
Published Sep 17, 2026 · Updated Sep 17, 2026
Initialization failure in the Linux sa2ul driver allows local users to interrupt crypto operations after DMA-pool creation fails. The sa_ul_probe() function ignores the error from sa_init_mem() and continues DMA setup and algorithm registration without the security-context pool needed by later requests. Exposure requires supported TI hardware and pool allocation failure during probing; public sources do not establish attacker control of that failure or a specific crash mode.
Summary
What happened
Initialization failure in the Linux sa2ul driver allows local users to interrupt crypto operations after DMA-pool creation fails. The sa_ul_probe() function ignores the error from sa_init_mem() and continues DMA setup and algorithm registration without the security-context pool needed by later requests. Exposure requires supported TI hardware and pool allocation failure during probing; public sources do not establish attacker control of that failure or a specific crash mode.
The record
- CVE
- CVE-2026-93158
- Published
- Sep 17, 2026
- Updated
- Sep 17, 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 17, 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=5.9
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <04c46784ec249cac995e31f0691397b82bdaa5fd
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <304dcd26bfc3ce6771c2bd3b7c0299dcfd5f4e06
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <91ded4742fcde6ad415c4d8a20e5ea0dcdf4f73e
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <9907426b438e4dbc8c45138bd440ad6d732d80b7
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <9a692a6a2b47328a36c8d80c7fbf81da16b6d6b1
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <b68b35ed97d3e18edb9dea500d88420a95006742
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <d03f980a25853f6a380895119a572a3bb1194e8d
- Affected versionversion=7694b6ca649fead1a57046935711bc82dfc78cfb <f72c7837614a9705f8b3021828d49c9f095803ba
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