CVE-2024-42273

{"id": "CVE-2024-42273", "cveTags": [], "metrics": {}, "published": "2024-08-17T09:15:08.450", "references": [{"url": "https://git.kernel.org/stable/c/0cd106612396656d6f1ca17ef192c6759bb60791", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/4239571c5db46a42f723b8fa8394039187c34439", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/5fd057160ab240dd816ae09b625395d54c297de1", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/8cb1f4080dd91c6e6b01dbea013a3f42341cb6a1", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid\n\nmkdir /mnt/test/comp\nf2fs_io setflags compression /mnt/test/comp\ndd if=/dev/zero of=/mnt/test/comp/testfile bs=16k count=1\ntruncate --size 13 /mnt/test/comp/testfile\n\nIn the above scenario, we can get a BUG_ON.\n kernel BUG at fs/f2fs/segment.c:3589!\n Call Trace:\n do_write_page+0x78/0x390 [f2fs]\n f2fs_outplace_write_data+0x62/0xb0 [f2fs]\n f2fs_do_write_data_page+0x275/0x740 [f2fs]\n f2fs_write_single_data_page+0x1dc/0x8f0 [f2fs]\n f2fs_write_multi_pages+0x1e5/0xae0 [f2fs]\n f2fs_write_cache_pages+0xab1/0xc60 [f2fs]\n f2fs_write_data_pages+0x2d8/0x330 [f2fs]\n do_writepages+0xcf/0x270\n __writeback_single_inode+0x44/0x350\n writeback_sb_inodes+0x242/0x530\n __writeback_inodes_wb+0x54/0xf0\n wb_writeback+0x192/0x310\n wb_workfn+0x30d/0x400\n\nThe reason is we gave CURSEG_ALL_DATA_ATGC to COMPR_ADDR where the\npage was set the gcing flag by set_cluster_dirty()."}, {"lang": "es", "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: f2fs: asigna CURSEG_ALL_DATA_ATGC si blkaddr es v\u00e1lido mkdir /mnt/test/comp f2fs_io setflags compresi\u00f3n /mnt/test/comp dd if=/dev/zero of=/mnt/test/ comp/testfile bs=16k count=1 truncate --size 13 /mnt/test/comp/testfile En el escenario anterior, podemos obtener un BUG_ON. \u00a1ERROR del kernel en fs/f2fs/segment.c:3589! Seguimiento de llamadas: do_write_page+0x78/0x390 [f2fs] f2fs_outplace_write_data+0x62/0xb0 [f2fs] f2fs_do_write_data_page+0x275/0x740 [f2fs] f2fs_write_single_data_page+0x1dc/0x8f0 [f2fs_write_multi_ p\u00e1ginas+0x1e5/0xae0 [f2fs] f2fs_write_cache_p\u00e1ginas+0xab1/0xc60 [f2fs ] f2fs_write_data_pages+0x2d8/0x330 [f2fs] do_writepages+0xcf/0x270 __writeback_single_inode+0x44/0x350 writeback_sb_inodes+0x242/0x530 __writeback_inodes_wb+0x54/0xf0 wb_writeback+0x192/0x3 10 wb_workfn+0x30d/0x400 La raz\u00f3n es que le dimos CURSEG_ALL_DATA_ATGC a COMPR_ADDR donde est\u00e1 la p\u00e1gina set_cluster_dirty() estableci\u00f3 la bandera gcing."}], "lastModified": "2024-08-19T12:59:59.177", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}