f2fs: fix to bail out in get_new_segment()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bb5eb8a5b222fa5092f60d5555867a05ebc3bdf2, Kernel ca860f507a61c7c3d4dde47b830a5c0d555cf83c and Kernel f0023d7a2a86999c8e1300e911d92f995a5310a8.
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to bail out in get_new_segment() ------------[ cut here ]------------ WARNING: CPU: 3 PID: 579 at fs/f2fs/segment.c:2832 new_curseg+0x5e8/0x6dc pc : new_curseg+0x5e8/0x6dc Call trace: new_curseg+0x5e8/0x6dc f2fs_allocate_data_block+0xa54/0xe28 do_write_page+0x6c/0x194 f2fs_do_write_node_page+0x38/0x78 __write_node_page+0x248/0x6d4 f2fs_sync_node_pages+0x524/0x72c f2fs_write_checkpoint+0x4bc/0x9b0 __checkpoint_and_complete_reqs+0x80/0x244 issue_checkpoint_thread+0x8c/0xec kthread+0x114/0x1bc ret_from_fork+0x10/0x20 get_new_segment() detects inconsistent status in between free_segmap and free_secmap, let's record such error into super block, and bail out get_new_segment() instead of continue using the segment.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.8, >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <bb5eb8a5b222fa5092f60d5555867a05ebc3bdf2, >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ca860f507a61c7c3d4dde47b830a5c0d555cf83c, >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <f0023d7a2a86999c8e1300e911d92f995a5310a8 | bb5eb8a5b222fa5092f60d5555867a05ebc3bdf2, ca860f507a61c7c3d4dde47b830a5c0d555cf83c, f0023d7a2a86999c8e1300e911d92f995a5310a8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket