Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

[REJECTED CVE] A vulnerability was identified in the ext4 filesystem of the Linux kernel, where a race condition in buffer_head read fault injection could lead to clearing the buffer_uptodate flag on active buffers. This occurred due to a non-atomic interaction between buffer read completion and fault injection, potentially causing inode bitmap read failures and warnings. An attacker with control over fault injection mechanisms could exploit this issue to trigger filesystem inconsistencies or denial-of-service (DoS) conditions by forcing invalid buffer states, leading to unexpected crashes or errors.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved: ext4: fix race in buffer_head read fault injection When I enabled ext4 debug for fault injection testing, I encountered the following warning: EXT4-fs error (device sda): ext4_read_inode_bitmap:201: comm fsstress: Cannot read inode bitmap - block_group = 8, inode_bitmap = 1051 WARNING: CPU: 0 PID: 511 at fs/buffer.c:1181 mark_buffer_dirty+0x1b3/0x1d0 The root cause of the issue lies in the improper implementation of ext4's buffer_head read fault injection. The actual completion of buffer_head read and the buffer_head fault injection are not atomic, which can lead to the uptodate flag being cleared on normally used buffer_heads in race conditions. [CPU0] [CPU1] [CPU2] ext4_read_inode_bitmap ext4_read_bh() <bh read complete> ext4_read_inode_bitmap if (buffer_uptodate(bh)) return bh jbd2_journ...