| 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-53221: f2fs: fix null-ptr-deref in f2fs_submit_page_bio() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| f2fs: fix null-ptr-deref in f2fs_submit_page_bio() |
| |
| There's issue as follows when concurrently installing the f2fs.ko |
| module and mounting the f2fs file system: |
| KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027] |
| RIP: 0010:__bio_alloc+0x2fb/0x6c0 [f2fs] |
| Call Trace: |
| <TASK> |
| f2fs_submit_page_bio+0x126/0x8b0 [f2fs] |
| __get_meta_page+0x1d4/0x920 [f2fs] |
| get_checkpoint_version.constprop.0+0x2b/0x3c0 [f2fs] |
| validate_checkpoint+0xac/0x290 [f2fs] |
| f2fs_get_valid_checkpoint+0x207/0x950 [f2fs] |
| f2fs_fill_super+0x1007/0x39b0 [f2fs] |
| mount_bdev+0x183/0x250 |
| legacy_get_tree+0xf4/0x1e0 |
| vfs_get_tree+0x88/0x340 |
| do_new_mount+0x283/0x5e0 |
| path_mount+0x2b2/0x15b0 |
| __x64_sys_mount+0x1fe/0x270 |
| do_syscall_64+0x5f/0x170 |
| entry_SYSCALL_64_after_hwframe+0x76/0x7e |
| |
| Above issue happens as the biset of the f2fs file system is not |
| initialized before register "f2fs_fs_type". |
| To address above issue just register "f2fs_fs_type" at the last in |
| init_f2fs_fs(). Ensure that all f2fs file system resources are |
| initialized. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53221 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.6 with commit f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and fixed in 6.6.72 with commit 8dddc12d03248755d9f709bc1eb9e3ea2bf1b322 |
| Issue introduced in 5.6 with commit f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and fixed in 6.11.11 with commit 32f5e291b7677495f98246eec573767430321c08 |
| Issue introduced in 5.6 with commit f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and fixed in 6.12.2 with commit 9e11b1d5fda972f6be60ab732976a7c8e064cd56 |
| Issue introduced in 5.6 with commit f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and fixed in 6.13 with commit b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa |
| |
| 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-53221 |
| 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/8dddc12d03248755d9f709bc1eb9e3ea2bf1b322 |
| https://git.kernel.org/stable/c/32f5e291b7677495f98246eec573767430321c08 |
| https://git.kernel.org/stable/c/9e11b1d5fda972f6be60ab732976a7c8e064cd56 |
| https://git.kernel.org/stable/c/b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa |
