Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-93140

udf: Mark LVID buffer as uptodate before marking it dirty

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 2.6.28, 2.6.33, 3.1, 3.3, 5.10.270, and 6 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: udf: Mark LVID buffer as uptodate before marking it dirty When an I/O error occurs while writing the Logical Volume Integrity Descriptor (LVID) buffer to the block device, the block layer's completion handler (`end_buffer_write_sync()`) clears the `BH_Uptodate` flag on the buffer. However, the buffer still contains valid LVID data in memory. If the filesystem is subsequently remounted read-write or synced, `udf_open_lvid()` or `udf_sync_fs()` will modify the LVID buffer and call `mark_buffer_dirty()`. This triggers a spurious `WARN_ON_ONCE(!buffer_uptodate(bh))` warning in `mark_buffer_dirty()` because the buffer is not marked uptodate, even though its in-memory contents are valid and are about to be overwritten. To prevent this spurious warning, unconditionally set the `BH_Uptodate` flag before calling `mark_buffer_dirty()` in `udf_open_lvid()` and `udf_sync_fs()`. This acknowledges that the in-memory buffer is valid and matches the workaround previously applied to `udf_close_lvid()` in commit 853a0c25baf9 ("udf: Mark LVID buffer as uptodate before marking it dirty"). Extending this workaround ensures consistent behavior across all LVID updates. Buffer I/O error on dev loop0, logical block 128, lost sync page write ------------[ cut here ]------------ !buffer_uptodate(bh) WARNING: fs/buffer.c:1087 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1087 ... Call Trace: <TASK> udf_open_lvid+0x369/0x5b0 fs/udf/super.c:2078 udf_reconfigure+0x336/0x540 fs/udf/super.c:679 reconfigure_super+0x232/0x8f0 fs/super.c:1080 vfs_cmd_reconfigure fs/fsopen.c:268 [inline] vfs_fsconfig_locked+0x171/0x320 fs/fsopen.c:297 __do_sys_fsconfig fs/fsopen.c:463 [inline] __se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 </TASK>

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in e6461ef34f91ad7dbffdf912b3d661a7dd892931; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in 359cea636f4a74a96c01a8050f155e12840c079a; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in a4c4e38b356ad4c1f90478124922917489137c08; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in 8034ddf4751d9143c5ef7eebe3d4f33218fdd378; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in ee477e5204f764444e60699280abf5936c2a6ae6; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in 11afe1912140f79d5af3091a54b181ef72fce1a5; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in c4058355d27488a3cd31c60c032335f77c4fdcfc; From 853a0c25baf96b028de1654bea1e0c8857eadf3d · fixed in fb0601134c7e51728bd098abc6909315de1e5d86; From 2.6.27.62 · fixed in 2.6.28; From 2.6.32.57 · fixed in 2.6.33; From 3.0.21 · fixed in 3.1; From 3.2.6 · fixed in 3.3

  • Linux Linux

    3.3

  • KernelLinux

    From 3.3.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6

References 8

git.kernel.org