[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091855-CVE-2023-53373-087e@gregkh>
Date: Thu, 18 Sep 2025 15:34:18 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53373: crypto: seqiv - Handle EBUSY correctly
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2023-53373 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 4.14.308 with commit cc4d0d4251748a8a68026938f4055d2ac47c5719
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 4.19.276 with commit 1effbddaff60eeef8017c6dea1ee0ed970164d14
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 5.4.235 with commit 63551e4b7cbcd9914258827699eb2cb6ed6e4a16
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 5.10.173 with commit ae849d2f48019ff9c104e32bf588ccbfb200e971
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 5.15.99 with commit 36ec108b7bd7e280edb22de028467bd09d644620
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.1.16 with commit 4d497e8b200a175094e0ac252ed878add39b8771
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.2.3 with commit 9477db935eb690f697d9bcc4f608927841bc8b36
Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.3 with commit 32e62025e5e52fbe4812ef044759de7010b15dbc
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53373
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
crypto/seqiv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/cc4d0d4251748a8a68026938f4055d2ac47c5719
https://git.kernel.org/stable/c/1effbddaff60eeef8017c6dea1ee0ed970164d14
https://git.kernel.org/stable/c/63551e4b7cbcd9914258827699eb2cb6ed6e4a16
https://git.kernel.org/stable/c/ae849d2f48019ff9c104e32bf588ccbfb200e971
https://git.kernel.org/stable/c/36ec108b7bd7e280edb22de028467bd09d644620
https://git.kernel.org/stable/c/4d497e8b200a175094e0ac252ed878add39b8771
https://git.kernel.org/stable/c/9477db935eb690f697d9bcc4f608927841bc8b36
https://git.kernel.org/stable/c/32e62025e5e52fbe4812ef044759de7010b15dbc
Powered by blists - more mailing lists