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.
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.
Metrics
Affected Vendors & Products
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Thu, 18 Sep 2025 13:45:00 +0000

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-09-18T13:33:20.264Z
Reserved: 2025-09-17T14:54:09.734Z
Link: CVE-2023-53373

No data.

Status : Received
Published: 2025-09-18T14:15:39.880
Modified: 2025-09-18T14:15:39.880
Link: CVE-2023-53373

No data.

No data.