CVE-2023-53373: crypto: seqiv - Handle EBUSY correctly
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 MAYBACKLOG, we also need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-free.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53373?
CVE-2023-53373 has been assessed with a medium severity rating, indicating potential for data exposure or denial of service.
How do I fix CVE-2023-53373?
To fix CVE-2023-53373, update the Linux kernel to the latest patched version where this vulnerability has been resolved.
What impact does CVE-2023-53373 have on systems?
CVE-2023-53373 can lead to improper handling of certain error states, potentially allowing for memory leaks or instability.
Is CVE-2023-53373 exploitable remotely?
CVE-2023-53373 is not considered remotely exploitable; exploitation typically requires local access to the affected system.
What versions of the Linux kernel are affected by CVE-2023-53373?
CVE-2023-53373 affects specific versions of the Linux kernel prior to the resolution, so checking the version in use is essential.