[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025012129-CVE-2024-57943-7a6e@gregkh>
Date: Tue, 21 Jan 2025 13:18:32 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57943: exfat: fix the new buffer was not zeroed before writing
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
exfat: fix the new buffer was not zeroed before writing
Before writing, if a buffer_head marked as new, its data must
be zeroed, otherwise uninitialized data in the page cache will
be written.
So this commit uses folio_zero_new_buffers() to zero the new
buffers before ->write_end().
The Linux kernel CVE team has assigned CVE-2024-57943 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 6630ea49103c3d45461e29b0f6eb0ce750aeb8f5 and fixed in 6.12.10 with commit 942c6f91ab8d82a41650e717940b4e577173762f
Issue introduced in 6.12 with commit 6630ea49103c3d45461e29b0f6eb0ce750aeb8f5 and fixed in 6.13 with commit 98e2fb26d1a9eafe79f46d15d54e68e014d81d8c
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-2024-57943
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/exfat/file.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/942c6f91ab8d82a41650e717940b4e577173762f
https://git.kernel.org/stable/c/98e2fb26d1a9eafe79f46d15d54e68e014d81d8c
Powered by blists - more mailing lists