Skip to content
CVE PROGRAM SOURCE RECORD5.5 Medium

CVE-2024-26685

nilfs2: fix potential bug in end_buffer_async_write

Read JSON ↗CVE.org ↗
Status
Published
Published
Updated
Assigning organization
Linux

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.

Affected products

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Linux Linux

Default version status: unaffected

  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < c4a09fdac625e64abe478dcf88bfa20406616928affected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < d31c8721e816eff5ca6573cc487754f357c093cdaffected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < f3e4963566f58726d3265a727116a42b591f6596affected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < 8fa90634ec3e9cc50f42dd605eec60f2d146ced8affected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < 6589f0f72f8edd1fa11adce4eedbd3615f2e78abaffected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < 2c3bdba00283a6c7a5b19481a59a730f46063803affected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < 626daab3811b772086aef1bf8eed3ffe6f523effaffected
  • 7f42ec3941560f0902fe3671e36f2c20ffd3af0a to < 5bc09b397cbf1221f8a8aacb1152650c9195b02baffected
  • ccebcc74c81d8399c7b204aea47c1f33b09c2b17affected
  • 831c87640d23ccb253a02e4901bd9a325b5e8c2daffected
  • d8974c7fe717ee8fb0706e35cc92e0bcdf660ec5affected
  • 8f67918af09fc0ffd426a9b6f87697976d3fbc7baffected
  • 3.2.52 to < 3.3affected
  • 3.4.83 to < 3.5affected
  • 3.10.16 to < 3.11affected
  • 3.11.5 to < 3.12affected

Linux Linux

Default version status: affected

  • 3.12affected
  • 0 to < 3.12unaffected
  • 4.19.307 to ≤ 4.19.*unaffected
  • 5.4.269 to ≤ 5.4.*unaffected
  • 5.10.210 to ≤ 5.10.*unaffected
  • 5.15.149 to ≤ 5.15.*unaffected
  • 6.1.79 to ≤ 6.1.*unaffected
  • 6.6.18 to ≤ 6.6.*unaffected
  • 6.7.6 to ≤ 6.7.*unaffected
  • 6.8 to ≤ *unaffected

References