BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-10-02

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: xts - Handle EBUSY correctly As it is xts only handles the special return value of EINPROGRESS, which means that in all other cases it will free data related to the request. However, as the caller of xts 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-01

Last Modified

2025-10-02

Generated

2026-07-06

AI Q&A

2025-10-01

EPSS Evaluated

2026-07-05

NVD

CVE-2023-53494

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 5.15.160 (inc) to 5.16 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's crypto subsystem, specifically in the xts module. The issue is that xts only handles the EINPROGRESS return value correctly, but it does not properly handle the EBUSY return value when the caller specifies MAY_BACKLOG. This can cause backlogged requests to trigger a use-after-free error, which means the system might free data that is still in use, potentially leading to crashes or other unexpected behavior.

Impact Analysis

The vulnerability can lead to use-after-free conditions in the Linux kernel's crypto xts module. This can cause system instability, crashes, or potentially allow attackers to exploit the kernel memory corruption to execute arbitrary code or cause denial of service.

Hi! I’m here to help you understand CVE-2023-53494. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70