CVE-2023-53373
published 2025-09-18CVE-2023-53373: 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…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
4.8th percentile
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.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < cc4d0d4251748a8a68026938f4055d2ac47c5719 | cc4d0d4251748a8a68026938f4055d2ac47c5719 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 1effbddaff60eeef8017c6dea1ee0ed970164d14 | 1effbddaff60eeef8017c6dea1ee0ed970164d14 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 63551e4b7cbcd9914258827699eb2cb6ed6e4a16 | 63551e4b7cbcd9914258827699eb2cb6ed6e4a16 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < ae849d2f48019ff9c104e32bf588ccbfb200e971 | ae849d2f48019ff9c104e32bf588ccbfb200e971 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 36ec108b7bd7e280edb22de028467bd09d644620 | 36ec108b7bd7e280edb22de028467bd09d644620 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 4d497e8b200a175094e0ac252ed878add39b8771 | 4d497e8b200a175094e0ac252ed878add39b8771 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 9477db935eb690f697d9bcc4f608927841bc8b36 | 9477db935eb690f697d9bcc4f608927841bc8b36 |
| linux | linux | >= 0a270321dbf948963aeb0e8382fe17d2c2eb3771 < 32e62025e5e52fbe4812ef044759de7010b15dbc | 32e62025e5e52fbe4812ef044759de7010b15dbc |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 2.6.25 < 4.14.308 | 4.14.308 |
| linux | linux_kernel | >= 4.15 < 4.19.276 | 4.19.276 |
| linux | linux_kernel | >= 4.20 < 5.4.235 | 5.4.235 |
| linux | linux_kernel | >= 5.11 < 5.15.99 | 5.15.99 |
| linux | linux_kernel | >= 5.16 < 6.1.16 | 6.1.16 |
| linux | linux_kernel | >= 5.5 < 5.10.173 | 5.10.173 |
| linux | linux_kernel | >= 6.2 < 6.2.3 | 6.2.3 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2023-53373: In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special ret
osv·2025-09-18·CVSS 7.8
CVE-2023-53373 [HIGH] CVE-2023-53373: In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special ret
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.
GHSA
GHSA-gxr7-4mfg-37c7: In the Linux kernel, the following vulnerability has been resolved:
crypto: seqiv - Handle EBUSY correctly
As it is seqiv only handles the special r
ghsa_unreviewed·2025-09-18
CVE-2023-53373 [HIGH] CWE-416 GHSA-gxr7-4mfg-37c7: In the Linux kernel, the following vulnerability has been resolved:
crypto: seqiv - Handle EBUSY correctly
As it is seqiv only handles the special r
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.
Red Hat
kernel: crypto: seqiv - Handle EBUSY correctly
vendor_redhat·2025-09-18·CVSS 7.8
CVE-2023-53373 [HIGH] CWE-416 kernel: crypto: seqiv - Handle EBUSY correctly
kernel: 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 MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way. Otherwise backlogged
requests will trigger a use-after-free.
Statement: The flaw is in the seqiv IV generator and can lead to a use-after-free when backlogged crypto requests return -EBUSY. Triggering it is easier locally by flooding the kernel crypto API (e.g. via AF_ALG or many concurrent AEAD requests) because the attacker must create backlog conditions. Remote triggering is
Debian
CVE-2023-53373: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: seq...
vendor_debian·2023·CVSS 7.8
CVE-2023-53373 [HIGH] CVE-2023-53373: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: seq...
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.
Scope: local
bookworm: resolved (fixed in 6.1.20-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: resolved (fixed in 6.1.20-1)
sid: resolved (fixed in 6.1.20-1)
trixie: resolved (fixed in 6.1.20-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1effbddaff60eeef8017c6dea1ee0ed970164d14https://git.kernel.org/stable/c/32e62025e5e52fbe4812ef044759de7010b15dbchttps://git.kernel.org/stable/c/36ec108b7bd7e280edb22de028467bd09d644620https://git.kernel.org/stable/c/4d497e8b200a175094e0ac252ed878add39b8771https://git.kernel.org/stable/c/63551e4b7cbcd9914258827699eb2cb6ed6e4a16https://git.kernel.org/stable/c/9477db935eb690f697d9bcc4f608927841bc8b36https://git.kernel.org/stable/c/ae849d2f48019ff9c104e32bf588ccbfb200e971https://git.kernel.org/stable/c/cc4d0d4251748a8a68026938f4055d2ac47c5719
2025-09-18
Published