Към съдържанието
Търсене

CVE-2026-23267: Linux

Няма оценка

CVSS

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

    Описание

    Оригинално описание

    In the Linux kernel, the following vulnerability has been resolved: f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes During SPO tests, when mounting F2FS, an -EINVAL error was returned from f2fs_recover_inode_page. The issue occurred under the following scenario Thread A Thread B f2fs_ioc_commit_atomic_write - f2fs_do_sync_file // atomic = true - f2fs_fsync_node_pages : last_folio = inode folio : schedule before folio_lock(last_folio) f2fs_write_checkpoint - block_operations// writeback last_folio - schedule before f2fs_flush_nat_entries : set_fsync_mark(last_folio, 1) : set_dentry_mark(last_folio, 1) : folio_mark_dirty(last_folio) - __write_node_folio(last_folio) : f2fs_down_read(&sbi->node_write)//block - f2fs_flush_nat_entries : {struct nat_entry}->flag |= BIT(IS_CHECKPOINTED) - unblock_operations : f2fs_up_write(&sbi->node_write) f2fs_write_checkpoint//return : f2fs_do_write_node_page() f2fs_ioc_commit_atomic_write//return SPO Thread A calls f2fs_need_dentry_mark(sbi, ino), and the last_folio has already been written once. However, the {struct nat_entry}->flag did not have the IS_CHECKPOINTED set, causing set_dentry_mark(last_folio, 1) and write last_folio again after Thread B finishes f2fs_write_checkpoint. After SPO and reboot, it was detected that {struct node_info}->blk_addr was not NULL_ADDR because Thread B successfully write the checkpoint. This issue only occurs in atomic write scenarios. For regular file fsync operations, the folio must be dirty. If blo

    Засегнати продукти

    • Linux Linux: 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди 32bc3c9fe18881d50dd51fd5f26d19fe1190dc0d; 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди 75e19da068adf0dc5dd269dd157392434b9117d4; 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди 962c167b0f262b9962207fbeaa531721d55ea00e; 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди bd66b4c487d5091d2a65d6089e0de36f0c26a4c7; 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди ed81bc5885460905f9160e7b463e5708fd056324; 608514deba38c8611ad330d6a3c8e2b9a1f68e4b преди 7633a7387eb4d0259d6bea945e1d3469cd135bbc
    • Linux Linux: 4.7; преди 4.7; 6.1.164 до 6.1.*; 6.6.127 до 6.6.*; 6.12.74 до 6.12.*; 6.18.13 до 6.18.*; 6.19.3 до 6.19.*; от 7.0 нататък

    История

    • 18 март 2026 Публикувано

    Други уязвимости в Linux Linux

    Първоизточници

    CVE-2026-23267: Linux | freedomonline.bg