Overview
About vulnerability
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to do sanity check on node footer in {read,write}_end_io
———–[ cut here ]————
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
In f2fs_write_end_io(), it detects there is inconsistency in between node page index (nid) and footer.nid of node page.
If footer of node page is corrupted in fuzzed image, then we load corrupted node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(), in where we won’t do sanity check on node footer, once node page becomes dirty, we will encounter this bug after node page writeback.
Details
- Affected product:
- AlmaLinux 9.2 ESU , CentOS 7 ELS , CentOS 8.4 ELS , CentOS 8.5 ELS , CentOS Stream 8 ELS , CloudLinux 7 ELS , Oracle Linux 7 ELS , RHEL 7 ELS , TuxCare 9.6 ESU , Ubuntu 16.04 ELS , Ubuntu 18.04 ELS , Ubuntu 20.04 ELS
- Affected packages:
- kernel @ 5.14.0 (+13 more)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to do sanity check on node footer in {read,write}_end_io
———–[ cut here ]————
kernel BUG at fs/f2fs/data.c:358!
Call Trace:
In f2fs_write_end_io(), it detects there is inconsistency in between node page index (nid) and footer.nid of node page.
If footer of node page is corrupted in fuzzed image, then we load corrupted node page w/ async method, e.g. f2fs_ra_node_pages() or f2fs_ra_node_page(), in where we won’t do sanity check on node footer, once node page becomes dirty, we will encounter this bug after node page writeback.