ext4: fix deadlock when converting an inline directory in nojournal mode
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock when converting an inline directory in nojournal mode In no journal mode, ext4_finish_convert_inline_dir() can self-deadlock by calling ext4_handle_dirty_dirblock() when it already has taken the directory lock. There is a similar self-deadlock in ext4_incvert_inline_data_nolock() for data files which we'll fix at the same time. A simple reproducer demonstrating the problem: mke2fs -Fq -t ext2 -O inline_data -b 4k /dev/vdc 64 mount -t ext4 -o dirsync /dev/vdc /vdc cd /vdc mkdir file0 cd file0 touch file0 touch file1 attr -s BurnSpaceInEA -V abcde . touch supercalifragilisticexpialidocious
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.8
References 7
git.kernel.org
- stable/c/b4fa4768c9acff77245d672d855d2c88294850b1
- stable/c/5f8b55136ad787aed2c184f7cb3e93772ae637a3
- stable/c/640c8c365999c6f23447ac766437236ad88317c5
- stable/c/665cc3ba50330049524c1d275bc840a8f28dde73
- stable/c/0b1c4357bb21d9770451a1bdb8d419ea10bada88
- stable/c/804de0c72cd473e186ca4e1f6287d45431b14e5a
- stable/c/f4ce24f54d9cca4f09a395f3eecce20d6bec4663