# CVE-2023-54046: crypto: essiv - Handle EBUSY correctly

> A use-after-free vulnerability in the Linux kernel's ESSIV crypto module allows attackers to cause denial of service or execute code via backlogged requests.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54046, DEBIAN-CVE-2023-54046, GHSA-m7wm-fq3g-5gmr, UBUNTU-CVE-2023-54046

## What is CVE-2023-54046?

CVE-2023-54046 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. 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: essiv - Handle EBUSY correctly

As it is essiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.

However, as the caller of essiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way.  Otherwise backlogged
requests will trigger a use-after-free.

## Which versions are affected by CVE-2023-54046?


## How do I fix CVE-2023-54046?

Apply the vendor's patch.

## Is CVE-2023-54046 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54046 and fix it if it is affected.

What it is: CVE-2023-54046 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. 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-2023-54046 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-2023-54046/ (Markdown: https://insights.sbomify.com/CVE-2023-54046/index.md)
```

## Sources

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

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