---
id: CVE-2023-54046
title: 'crypto: essiv - Handle EBUSY correctly'
summary: |-
  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 relat…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    c61e7d182ee3f3f5ecf18a2964e303d49c539b52
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    796e02cca30a67322161f0745e5ce994bbe75605
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    840a1d3b77c1b062bd62b4733969a5b1efc274ce
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    69c67d451fc19d88e54f7d97e8e7c093e08357e1
  - >-
    Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 <
    b5a772adf45a32c68bef28e60621f12617161556
  - Linux 5.4
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-15T21:38:04.568323Z'
published: '2025-12-24'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T21:41:38.544Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2023-54046'
references:
  - url: 'https://git.kernel.org/stable/c/c61e7d182ee3f3f5ecf18a2964e303d49c539b52'
  - url: 'https://git.kernel.org/stable/c/796e02cca30a67322161f0745e5ce994bbe75605'
  - url: 'https://git.kernel.org/stable/c/840a1d3b77c1b062bd62b4733969a5b1efc274ce'
  - url: 'https://git.kernel.org/stable/c/a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385'
  - url: 'https://git.kernel.org/stable/c/69c67d451fc19d88e54f7d97e8e7c093e08357e1'
  - url: 'https://git.kernel.org/stable/c/b5a772adf45a32c68bef28e60621f12617161556'
tags:
  - cve.org
epss: 0.00196
epssPercentile: 0.08704
ingestedAt: '2026-10-15T22:48:25.426Z'
---

## Overview

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.

## Affected

- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < c61e7d182ee3f3f5ecf18a2964e303d49c539b52`
- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < 796e02cca30a67322161f0745e5ce994bbe75605`
- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < 840a1d3b77c1b062bd62b4733969a5b1efc274ce`
- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385`
- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < 69c67d451fc19d88e54f7d97e8e7c093e08357e1`
- `Linux >= be1eb7f78aa8fbe34779c56c266ccd0364604e71 < b5a772adf45a32c68bef28e60621f12617161556`
- `Linux 5.4`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
