From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52641: fs/ntfs3: Add NULL ptr dereference checking at the end of attr_allocate_frame()
Date: Wed, 3 Apr 2024 19:30:57 +0200 [thread overview]
Message-ID: <2024040357-CVE-2023-52641-1c18@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Add NULL ptr dereference checking at the end of attr_allocate_frame()
It is preferable to exit through the out: label because
internal debugging functions are located there.
The Linux kernel CVE team has assigned CVE-2023-52641 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.150 with commit ee8db6475cb1
Fixed in 6.1.80 with commit 50545eb6cd5f
Fixed in 6.6.19 with commit 947c3f3d31ea
Fixed in 6.7.7 with commit 847b68f58c21
Fixed in 6.8 with commit aaab47f204aa
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-52641
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/ntfs3/attrib.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/ee8db6475cb15c8122855f72ad4cfa5375af6a7b
https://git.kernel.org/stable/c/50545eb6cd5f7ff852a01fa29b7372524ef948cc
https://git.kernel.org/stable/c/947c3f3d31ea185ddc8e7f198873f17d36deb24c
https://git.kernel.org/stable/c/847b68f58c212f0439c5a8101b3841f32caffccd
https://git.kernel.org/stable/c/aaab47f204aaf47838241d57bf8662c8840de60a
reply other threads:[~2024-04-03 17:31 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=2024040357-CVE-2023-52641-1c18@gregkh \
--to=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.