# CVE-2026-93155: crypto: keembay - Fix AEAD unregister count in error path

> A bug in the Linux kernel's Keembay crypto driver causes incorrect cleanup during error handling, potentially leading to system instability or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102314, BELL-CVE-2026-93155, DEBIAN-CVE-2026-93155, GHSA-h6fj-2f26-g348, UBUNTU-CVE-2026-93155

## What is CVE-2026-93155?

CVE-2026-93155 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93155?


## How do I fix CVE-2026-93155?

Apply the vendor's patch.

## Is CVE-2026-93155 being exploited?

There is no known exploitation of CVE-2026-93155 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93155 and fix it if it is affected.

What it is: CVE-2026-93155 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93155 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93155/ (Markdown: https://insights.sbomify.com/CVE-2026-93155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93155
- OSV: https://osv.dev/vulnerability/CVE-2026-93155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93155/
Summaries are generated and may contain mistakes; the official description above is the record.