GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel crypto/essiv: EBUSY from a backlogged request frees live data, giving a use-after-free

CVSS 7.8CVE-2023-54046Kernel, userspace & hypervisorcurated

Impact

The essiv template only treated -EINPROGRESS as a non-terminal return and freed request-related data for every other value, so a caller using MAY_BACKLOG that gets -EBUSY has its data freed while the request is still queued - a use-after-free in kernel crypto context. essiv is the IV generator used by dm-crypt, so this sits under encrypted local NVMe on GPU nodes where encryption-at-rest is mandated. The failure needs the crypto backlog to be full, which happens under heavy parallel I/O rather than on an idle host.

Who can reach it

Local - requires I/O through a dm-crypt volume configured with an essiv IV generator and enough concurrency to fill the crypto backlog. No network path and no special capability beyond writing to the encrypted volume.

What to do

Update to a stable kernel containing the essiv EBUSY fix (commits 69c67d451fc1, 796e02cca30a, 840a1d3b77c1, a006aa3eedb8, b5a772adf45a) and reboot the node; dm-crypt volumes cannot be re-stacked under live workloads. No mitigation short of patching is described in the record.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.