From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52436: f2fs: explicitly null-terminate the xattr list
Date: Tue, 20 Feb 2024 19:33:54 +0100 [thread overview]
Message-ID: <2024022056-operative-cork-082c@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
f2fs: explicitly null-terminate the xattr list
When setting an xattr, explicitly null-terminate the xattr list. This
eliminates the fragile assumption that the unused xattr space is always
zeroed.
The Linux kernel CVE team has assigned CVE-2023-52436 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.306 with commit 16ae3132ff77
Fixed in 5.4.268 with commit 12cf91e23b12
Fixed in 5.10.209 with commit 3e47740091b0
Fixed in 5.15.148 with commit 32a6cfc67675
Fixed in 6.1.74 with commit 5de9e9dd1828
Fixed in 6.6.13 with commit 2525d1ba225b
Fixed in 6.7.1 with commit f6c30bfe5a49
Fixed in 6.8-rc1 with commit e26b6d39270f
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-52436
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:
fs/f2fs/xattr.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/16ae3132ff7746894894927c1892493693b89135
https://git.kernel.org/stable/c/12cf91e23b126718a96b914f949f2cdfeadc7b2a
https://git.kernel.org/stable/c/3e47740091b05ac8d7836a33afd8646b6863ca52
https://git.kernel.org/stable/c/32a6cfc67675ee96fe107aeed5af9776fec63f11
https://git.kernel.org/stable/c/5de9e9dd1828db9b8b962f7ca42548bd596deb8a
https://git.kernel.org/stable/c/2525d1ba225b5c167162fa344013c408e8b4de36
https://git.kernel.org/stable/c/f6c30bfe5a49bc38cae985083a11016800708fea
https://git.kernel.org/stable/c/e26b6d39270f5eab0087453d9b544189a38c8564
reply other threads:[~2024-02-20 18:34 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=2024022056-operative-cork-082c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@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).