CVE-2026-92476: crypto: keembay - Initialize completion before requesting IRQ
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 4ce407055ae9d37f46a3c6f05eb27198b354d287, 5aae80dcec0748b4ed61daace2ad8b12082261f2, 7efb51a5893b22003a679d088b7794be2ccd6c32; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 4ce407055ae9d37f46a3c6f05eb27198b354d287, 5aae80dcec0748b4ed61daace2ad8b12082261f2, 7efb51a5893b22003a679d088b7794be2ccd6c32; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: crypto: keembay - Initialize completion before requesting IRQ kmb_ocs_aes_probe() requests the device IRQ before initializing irq_completion. Once the handler is registered it can run immediately, and ocs_aes_irq_handler() unconditionally calls complete(). An interrupt in this window would therefore use an uninitialized completion. Initialize the completion before requesting the IRQ, as the sibling OCS HCU and ECC drivers already do.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.11affected
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before a3ffced8be1555f283680065c3b87a19f5ab9097affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 4ce407055ae9d37f46a3c6f05eb27198b354d287affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before d52a15c4559b69805bc69bf4ad9e16bbf6480d52affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before f8970ee9e315c9e2258ae8914d5fb32b1039d2f6affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 7efb51a5893b22003a679d088b7794be2ccd6c32affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 5aae80dcec0748b4ed61daace2ad8b12082261f2affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before fce20289dd622cc7ab78d72c8a979a9f8b7cb10eaffected · git
- before 5.11not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90434Sep 17, 2026 · isofs: release zisofs block pointer buffer head0Monitor
- ← EarlierCVE-2026-90435Sep 17, 2026 · RDMA/mlx5: Fix integer overflow of user QP buffer size31Monitor
- Later →CVE-2026-92477Sep 17, 2026 · scsi: ufs: debugfs: Reserve space for a string terminator0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4ce407055ae9d37f46a3c6f05eb27198b354d287 | Vendor (CNA) |
| Linux Linux | 5aae80dcec0748b4ed61daace2ad8b12082261f2 | Vendor (CNA) |
| Linux Linux | 7efb51a5893b22003a679d088b7794be2ccd6c32 | Vendor (CNA) |
| Linux Linux | a3ffced8be1555f283680065c3b87a19f5ab9097 | Vendor (CNA) |
| Linux Linux | d52a15c4559b69805bc69bf4ad9e16bbf6480d52 | Vendor (CNA) |
| Linux Linux | f8970ee9e315c9e2258ae8914d5fb32b1039d2f6 | Vendor (CNA) |
| Linux Linux | fce20289dd622cc7ab78d72c8a979a9f8b7cb10e | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5aae80dcec0748b4ed61daace2ad8b12082261f2
- git.kernel.org/stable/c/7efb51a5893b22003a679d088b7794be2ccd6c32
- git.kernel.org/stable/c/a3ffced8be1555f283680065c3b87a19f5ab9097
- git.kernel.org/stable/c/d52a15c4559b69805bc69bf4ad9e16bbf6480d52
- git.kernel.org/stable/c/f8970ee9e315c9e2258ae8914d5fb32b1039d2f6
- git.kernel.org/stable/c/fce20289dd622cc7ab78d72c8a979a9f8b7cb10e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.