blob: b771efb372a195bb379ac7806a94df58f8d155b9 [file] [log] [blame]
From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-47726: f2fs: fix to wait dio completion
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to wait dio completion
It should wait all existing dio write IOs before block removal,
otherwise, previous direct write IO may overwrite data in the
block which may be reused by other inode.
The Linux kernel CVE team has assigned CVE-2024-47726 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.235 with commit 7be13b73409b553d9d9a6cbb042b4d19e2631cc7
Fixed in 5.15.179 with commit 3aa5254d80969cb576601fb9fec7a188cc8dc169
Fixed in 6.1.129 with commit f81302decd64245bb1bd154ecae0f65a9ee21f04
Fixed in 6.6.70 with commit c2a7fc514637f640ff55c3f3e3ed879970814a3f
Fixed in 6.11.2 with commit e3db757ff9b7101ae68650ac5f6dd5743b68164e
Fixed in 6.12 with commit 96cfeb0389530ae32ade8a48ae3ae1ac3b6c009d
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-47726
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/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/7be13b73409b553d9d9a6cbb042b4d19e2631cc7
https://git.kernel.org/stable/c/3aa5254d80969cb576601fb9fec7a188cc8dc169
https://git.kernel.org/stable/c/f81302decd64245bb1bd154ecae0f65a9ee21f04
https://git.kernel.org/stable/c/c2a7fc514637f640ff55c3f3e3ed879970814a3f
https://git.kernel.org/stable/c/e3db757ff9b7101ae68650ac5f6dd5743b68164e
https://git.kernel.org/stable/c/96cfeb0389530ae32ade8a48ae3ae1ac3b6c009d