Denial of service via uninitialized IRQ completion
Published Sep 17, 2026 · Updated Sep 17, 2026
An IRQ initialization race in Linux's Keem Bay AES driver allows local users to disrupt kernel operation during device probing. kmb_ocs_aes_probe() registers the IRQ before initializing irq_completion, allowing ocs_aes_irq_handler() to call complete() on an uninitialized object. The race requires an interrupt during that probing window on relevant hardware; upstream does not specify whether the resulting disruption is a hang or crash.
Summary
What happened
An IRQ initialization race in Linux's Keem Bay AES driver allows local users to disrupt kernel operation during device probing. kmb_ocs_aes_probe() registers the IRQ before initializing irq_completion, allowing ocs_aes_irq_handler() to call complete() on an uninitialized object. The race requires an interrupt during that probing window on relevant hardware; upstream does not specify whether the resulting disruption is a hang or crash.
The record
- CVE
- CVE-2026-92476
- 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.11
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <4ce407055ae9d37f46a3c6f05eb27198b354d287
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <5aae80dcec0748b4ed61daace2ad8b12082261f2
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <7efb51a5893b22003a679d088b7794be2ccd6c32
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <a3ffced8be1555f283680065c3b87a19f5ab9097
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <d52a15c4559b69805bc69bf4ad9e16bbf6480d52
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <f8970ee9e315c9e2258ae8914d5fb32b1039d2f6
- Affected versionversion=88574332451380f4b51f6ca88ab9810e714bfb9b <fce20289dd622cc7ab78d72c8a979a9f8b7cb10e
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