CVE - CVE-2024-26685

CVE-ID
CVE-2024-26685	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buffers() and nilfs_lookup_node_buffers() and the resulting crash. This modification is safe as long as it is used for file data and b-tree node blocks where the page caches are independent. However, it was irrelevant and redundant to also introduce async_write for segment summary and super root blocks that share buffers with the backing device. This led to the possibility that the BUG_ON check in end_buffer_async_write would fail as described above, if independent writebacks of the backing device occurred in parallel. The use of async_write for segment summary buffers has already been removed in a previous change. Fix this issue by removing the manipulation of the async_write flag for the remaining super root block buffer.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/2c3bdba00283a6c7a5b19481a59a730f46063803 URL:https://git.kernel.org/stable/c/2c3bdba00283a6c7a5b19481a59a730f46063803 MISC:https://git.kernel.org/stable/c/5bc09b397cbf1221f8a8aacb1152650c9195b02b URL:https://git.kernel.org/stable/c/5bc09b397cbf1221f8a8aacb1152650c9195b02b MISC:https://git.kernel.org/stable/c/626daab3811b772086aef1bf8eed3ffe6f523eff URL:https://git.kernel.org/stable/c/626daab3811b772086aef1bf8eed3ffe6f523eff MISC:https://git.kernel.org/stable/c/6589f0f72f8edd1fa11adce4eedbd3615f2e78ab URL:https://git.kernel.org/stable/c/6589f0f72f8edd1fa11adce4eedbd3615f2e78ab MISC:https://git.kernel.org/stable/c/8fa90634ec3e9cc50f42dd605eec60f2d146ced8 URL:https://git.kernel.org/stable/c/8fa90634ec3e9cc50f42dd605eec60f2d146ced8 MISC:https://git.kernel.org/stable/c/c4a09fdac625e64abe478dcf88bfa20406616928 URL:https://git.kernel.org/stable/c/c4a09fdac625e64abe478dcf88bfa20406616928 MISC:https://git.kernel.org/stable/c/d31c8721e816eff5ca6573cc487754f357c093cd URL:https://git.kernel.org/stable/c/d31c8721e816eff5ca6573cc487754f357c093cd MISC:https://git.kernel.org/stable/c/f3e4963566f58726d3265a727116a42b591f6596 URL:https://git.kernel.org/stable/c/f3e4963566f58726d3265a727116a42b591f6596
Assigning CNA
kernel.org
Date Record Created
20240219	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240219)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)