| 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-40969: f2fs: don't set RO when shutting down f2fs |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| f2fs: don't set RO when shutting down f2fs |
| |
| Shutdown does not check the error of thaw_super due to readonly, which |
| causes a deadlock like below. |
| |
| f2fs_ioc_shutdown(F2FS_GOING_DOWN_FULLSYNC) issue_discard_thread |
| - bdev_freeze |
| - freeze_super |
| - f2fs_stop_checkpoint() |
| - f2fs_handle_critical_error - sb_start_write |
| - set RO - waiting |
| - bdev_thaw |
| - thaw_super_locked |
| - return -EINVAL, if sb_rdonly() |
| - f2fs_stop_discard_thread |
| -> wait for kthread_stop(discard_thread); |
| |
| The Linux kernel CVE team has assigned CVE-2024-40969 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.6.36 with commit 1036d3ea7a32cb7cee00885c73a1f2ba7fbc499a |
| Fixed in 6.9.7 with commit f47ed3b284b38f235355e281f57dfa8fffcc6563 |
| Fixed in 6.10 with commit 3bdb7f161697e2d5123b89fe1778ef17a44858e7 |
| |
| 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-40969 |
| 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/super.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/1036d3ea7a32cb7cee00885c73a1f2ba7fbc499a |
| https://git.kernel.org/stable/c/f47ed3b284b38f235355e281f57dfa8fffcc6563 |
| https://git.kernel.org/stable/c/3bdb7f161697e2d5123b89fe1778ef17a44858e7 |
