CVE-2026-93155: crypto: keembay - Fix AEAD unregister count in error path
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 27ec91c29ee155cc507b2f56221fc6fab65dbb51, 5607b101d86cbee8dd1ffab784495c880ca73383, 5bbb726d27ff6dff750264e51aa665538394d0f8.
Low priority for now. Upgrade to Linux Linux 27ec91c29ee155cc507b2f56221fc6fab65dbb51, 5607b101d86cbee8dd1ffab784495c880ca73383, 5bbb726d27ff6dff750264e51aa665538394d0f8 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 - Fix AEAD unregister count in error path register_aes_algs() registers the AEAD algorithms before registering the skcipher algorithms. If skcipher registration fails, the function unwinds the earlier AEAD registration with crypto_engine_unregister_aeads(), but it passes ARRAY_SIZE(algs), which is the skcipher table size. Use ARRAY_SIZE(algs_aead) for the AEAD unwind path so the unregister helper iterates over the same table that was registered. Also clarify the nearby comment: the crypto registration helpers clean up algorithms registered within the same call, while this function must still unwind earlier successful registration steps.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th 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 ccfaccc35e5a911ec1748291ea505e03b1ac03d9affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 27ec91c29ee155cc507b2f56221fc6fab65dbb51affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 5607b101d86cbee8dd1ffab784495c880ca73383affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before 5bbb726d27ff6dff750264e51aa665538394d0f8affected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before a3217fe7998622728a53dff405615e0971949eafaffected · git
- 88574332451380f4b51f6ca88ab9810e714bfb9b and later · before e264401ce4776a288524e5b87593d4d864147115affected · git
- before 5.11not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*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 | from 0 | — |
| 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-93153Sep 17, 2026 · RDMA/bng_re: return a timeout when firmware responses stall0Monitor
- ← EarlierCVE-2026-93154Sep 17, 2026 · RDMA/irdma: Add refcounting to user ring MRs31Monitor
- Later →CVE-2026-93156Sep 17, 2026 · crypto: rk3288 - fail ahash requests on HASH idle timeout0Monitor
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 | 27ec91c29ee155cc507b2f56221fc6fab65dbb51 | Vendor (CNA) |
| Linux Linux | 5607b101d86cbee8dd1ffab784495c880ca73383 | Vendor (CNA) |
| Linux Linux | 5bbb726d27ff6dff750264e51aa665538394d0f8 | Vendor (CNA) |
| Linux Linux | a3217fe7998622728a53dff405615e0971949eaf | Vendor (CNA) |
| Linux Linux | ccfaccc35e5a911ec1748291ea505e03b1ac03d9 | Vendor (CNA) |
| Linux Linux | e264401ce4776a288524e5b87593d4d864147115 | Vendor (CNA) |
| 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 (5 more)Show less
- git.kernel.org/stable/c/5607b101d86cbee8dd1ffab784495c880ca73383
- git.kernel.org/stable/c/5bbb726d27ff6dff750264e51aa665538394d0f8
- git.kernel.org/stable/c/a3217fe7998622728a53dff405615e0971949eaf
- git.kernel.org/stable/c/ccfaccc35e5a911ec1748291ea505e03b1ac03d9
- git.kernel.org/stable/c/e264401ce4776a288524e5b87593d4d864147115
Vendor advisories and official records. Exploit/PoC links are deliberately left out.