f2fs: fix to wait on block writeback for post_read case
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2bfe8fdb674f71747553a65f2ef27e14c8880655, Kernel 4535be48780431753505e74e1b1ad4836a189bc2, Kernel 55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait on block writeback for post_read case If inode is compressed, but not encrypted, it missed to call f2fs_wait_on_block_writeback() to wait for GCed page writeback in IPU write path. Thread A GC-Thread - f2fs_gc - do_garbage_collect - gc_data_segment - move_data_block - f2fs_submit_page_write migrate normal cluster's block via meta_inode's page cache - f2fs_write_single_data_page - f2fs_do_write_data_page - f2fs_inplace_write_data - f2fs_submit_page_bio IRQ - f2fs_read_end_io IRQ old data overrides new data due to out-of-order GC and common IO. - f2fs_read_end_io
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.6, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <2bfe8fdb674f71747553a65f2ef27e14c8880655, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <4535be48780431753505e74e1b1ad4836a189bc2, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <9bfd5ea71521d0e522ba581c6ccc5db93759c0c3, >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <f904c156d8011d8291ffd5b6b398f3747e294986 | 2bfe8fdb674f71747553a65f2ef27e14c8880655, 4535be48780431753505e74e1b1ad4836a189bc2, 55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00, 9bfd5ea71521d0e522ba581c6ccc5db93759c0c3, f904c156d8011d8291ffd5b6b398f3747e294986 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket