CVE-2023-53373
crypto: seqiv - Handle EBUSY correctly
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv 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 seqiv 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.
INFO
Published Date :
Sept. 18, 2025, 2:15 p.m.
Last Modified :
Sept. 18, 2025, 2:15 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2023-53373
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the latest Linux kernel updates.
- Ensure crypto: seqiv handles EBUSY correctly.
- Test for successful backlogged request processing.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-53373.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-53373 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-53373
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-53373 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-53373 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 18, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv 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 seqiv 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. Added Reference https://git.kernel.org/stable/c/1effbddaff60eeef8017c6dea1ee0ed970164d14 Added Reference https://git.kernel.org/stable/c/32e62025e5e52fbe4812ef044759de7010b15dbc Added Reference https://git.kernel.org/stable/c/36ec108b7bd7e280edb22de028467bd09d644620 Added Reference https://git.kernel.org/stable/c/4d497e8b200a175094e0ac252ed878add39b8771 Added Reference https://git.kernel.org/stable/c/63551e4b7cbcd9914258827699eb2cb6ed6e4a16 Added Reference https://git.kernel.org/stable/c/9477db935eb690f697d9bcc4f608927841bc8b36 Added Reference https://git.kernel.org/stable/c/ae849d2f48019ff9c104e32bf588ccbfb200e971 Added Reference https://git.kernel.org/stable/c/cc4d0d4251748a8a68026938f4055d2ac47c5719