From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()
Date: Tue, 7 Oct 2025 17:21:35 +0200 [thread overview]
Message-ID: <2025100707-CVE-2023-53676-e7fb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()
The function lio_target_nacl_info_show() uses sprintf() in a loop to print
details for every iSCSI connection in a session without checking for the
buffer length. With enough iSCSI connections it's possible to overflow the
buffer provided by configfs and corrupt the memory.
This patch replaces sprintf() with sysfs_emit_at() that checks for buffer
boundries.
The Linux kernel CVE team has assigned CVE-2023-53676 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.326 with commit df349e84c2cb0dd05d98c8e1189c26ab4b116083
Fixed in 4.19.295 with commit 114b44dddea1f8f99576de3c0e6e9059012002fc
Fixed in 5.4.257 with commit 2cbe6a88fbdd6e8aeab358eef61472e2de43d6f6
Fixed in 5.10.197 with commit bbe3ff47bf09db8956bc2eeb49d2d514d256ad2a
Fixed in 5.15.133 with commit 5353df78c22623b42a71d51226d228a8413097e2
Fixed in 6.1.55 with commit 4738bf8b2d3635c2944b81b2a84d97b8c8b0978d
Fixed in 6.5.5 with commit 0cac6cbb9908309352a5d30c1876882771d3da50
Fixed in 6.6 with commit 801f287c93ff95582b0a2d2163f12870a2f076d4
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-53676
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:
drivers/target/iscsi/iscsi_target_configfs.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/df349e84c2cb0dd05d98c8e1189c26ab4b116083
https://git.kernel.org/stable/c/114b44dddea1f8f99576de3c0e6e9059012002fc
https://git.kernel.org/stable/c/2cbe6a88fbdd6e8aeab358eef61472e2de43d6f6
https://git.kernel.org/stable/c/bbe3ff47bf09db8956bc2eeb49d2d514d256ad2a
https://git.kernel.org/stable/c/5353df78c22623b42a71d51226d228a8413097e2
https://git.kernel.org/stable/c/4738bf8b2d3635c2944b81b2a84d97b8c8b0978d
https://git.kernel.org/stable/c/0cac6cbb9908309352a5d30c1876882771d3da50
https://git.kernel.org/stable/c/801f287c93ff95582b0a2d2163f12870a2f076d4
reply other threads:[~2025-10-07 15:25 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=2025100707-CVE-2023-53676-e7fb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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