Bug 2400777 (CVE-2023-53494) - CVE-2023-53494 kernel: crypto: xts - Handle EBUSY correctly
Summary: CVE-2023-53494 kernel: crypto: xts - Handle EBUSY correctly
Keywords:
Status: NEW
Alias: CVE-2023-53494
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-01 12:06 UTC by OSIDB Bzimport
Modified: 2025-11-19 12:27 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:19409 0 None None None 2025-11-03 02:27:15 UTC
Red Hat Product Errata RHSA-2025:21051 0 None None None 2025-11-12 00:31:35 UTC
Red Hat Product Errata RHSA-2025:21091 0 None None None 2025-11-12 08:09:05 UTC
Red Hat Product Errata RHSA-2025:21112 0 None None None 2025-11-12 11:25:22 UTC
Red Hat Product Errata RHSA-2025:21128 0 None None None 2025-11-12 13:48:58 UTC
Red Hat Product Errata RHSA-2025:21136 0 None None None 2025-11-12 15:05:32 UTC
Red Hat Product Errata RHSA-2025:21760 0 None None None 2025-11-19 12:27:27 UTC

Description OSIDB Bzimport 2025-10-01 12:06:50 UTC 
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.
Comment 1 Jon Moroney 2025-10-01 19:51:11 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025100124-CVE-2023-53494-6542@gregkh/T
Comment 4 errata-xmlrpc 2025-11-03 02:27:14 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:19409 https://access.redhat.com/errata/RHSA-2025:19409
Comment 7 errata-xmlrpc 2025-11-12 00:31:34 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2025:21051 https://access.redhat.com/errata/RHSA-2025:21051
Comment 8 errata-xmlrpc 2025-11-12 08:09:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:21091 https://access.redhat.com/errata/RHSA-2025:21091
Comment 9 errata-xmlrpc 2025-11-12 11:25:21 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:21112 https://access.redhat.com/errata/RHSA-2025:21112
Comment 10 errata-xmlrpc 2025-11-12 13:48:57 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2025:21128 https://access.redhat.com/errata/RHSA-2025:21128
Comment 11 errata-xmlrpc 2025-11-12 15:05:31 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:21136 https://access.redhat.com/errata/RHSA-2025:21136
Comment 12 errata-xmlrpc 2025-11-19 12:27:27 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2025:21760 https://access.redhat.com/errata/RHSA-2025:21760
Note You need to log in before you can comment on or make changes to this bug.