From: Lee Jones <lee@kernel.org>
To: linux-cve-announce@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>
Subject: CVE-2023-52612: crypto: scomp - fix req->dst buffer overflow
Date: Mon, 18 Mar 2024 10:08:02 +0000 [thread overview]
Message-ID: <20240318100758.2828621-12-lee@kernel.org> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: scomp - fix req->dst buffer overflow
The req->dst buffer size should be checked before copying from the
scomp_scratch->dst to avoid req->dst buffer overflow problem.
The Linux kernel CVE team has assigned CVE-2023-52612 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 4.19.306 with commit 1142d65c5b88
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 5.4.268 with commit e0e3f4a18784
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 5.10.209 with commit 4518dc468cdd
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 5.15.148 with commit a5f2f91b3fd7
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 6.1.75 with commit 4df0c942d04a
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 6.6.14 with commit 7d9e5bed036a
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 6.7.2 with commit 71c6670f9f03
Issue introduced in 4.10 with commit 1ab53a77b772 and fixed in 6.8 with commit 744e1885922a
Please see https://www.kernel.org or 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-52612
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/scompress.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/1142d65c5b881590962ad763f94505b6dd67d2fe
https://git.kernel.org/stable/c/e0e3f4a18784182cfe34e20c00eca11e78d53e76
https://git.kernel.org/stable/c/4518dc468cdd796757190515a9be7408adc8911e
https://git.kernel.org/stable/c/a5f2f91b3fd7387e5102060809316a0f8f0bc625
https://git.kernel.org/stable/c/4df0c942d04a67df174195ad8082f6e30e7f71a5
https://git.kernel.org/stable/c/7d9e5bed036a7f9e2062a137e97e3c1e77fb8759
https://git.kernel.org/stable/c/71c6670f9f032ec67d8f4e3f8db4646bf5a62883
https://git.kernel.org/stable/c/744e1885922a9943458954cfea917b31064b4131
reply other threads:[~2024-03-18 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240318100758.2828621-12-lee@kernel.org \
--to=lee@kernel.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).