All reports
Low

kernel: crypto: essiv - Handle EBUSY correctly

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-54046

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-19

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.

A use-after-free vulnerability was found in the Linux kernel's ESSIV (Encrypted Salt-Sector Initialization Vector) crypto module. The essiv code only handles EINPROGRESS as a special return value, freeing request data for all other return codes. When callers use MAY_BACKLOG, an EBUSY return indicates the request was queued but will complete later. Freeing the data on EBUSY causes a use-after-free when the backlogged request completes.