ext4: make sure the first directory block is not a hole
- 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
- Fix
- Fixed in 4.19.320, 4.10, 4.15, 5.2, 5.3, and 6 more
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: make sure the first directory block is not a hole The syzbot constructs a directory that has no dirblock but is non-inline, i.e. the first directory block is a hole. And no errors are reported when creating files in this directory in the following flow. ext4_mknod ... ext4_add_entry // Read block 0 ext4_read_dirblock(dir, block, DIRENT) bh = ext4_bread(NULL, inode, block, 0) if (!bh && (type == INDEX || type == DIRENT_HTREE)) // The first directory block is a hole // But type == DIRENT, so no error is reported. After that, we get a directory block without '.' and '..' but with a valid dentry. This may cause some code that relies on dot or dotdot (such as make_indexed_dir()) to crash. Therefore when ext4_read_dirblock() finds that the first directory block is a hole report that the filesystem is corrupted and return an error to avoid loading corrupted data from disk causing something bad.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 3a17ca864baffc0c6f6e8aad525aa4365775a193 · fixed in d81d7e347d1f1f48a5634607d39eb90c161c8afe; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in e02f9941e8c011aa3eafa799def6a134ce06bcfa; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in de2a011a13a46468a6e8259db58b1b62071fe136; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in 9771e3d8365ae1dd5e8846a204cb9af14e3e656a; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in b609753cbbd38f8c0affd4956c0af178348523ac; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in c3893d9de8ee153baac56d127d844103488133b5; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in 299bc6ffa57e04e74c6cce866d6c0741fb4897a1; From 4e19d6b65fb4fc42e352ce9883649e049da14743 · fixed in f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6; From 4.19.62 · fixed in 4.19.320; From 4.9.187 · fixed in 4.10; From 4.14.135 · fixed in 4.15; From 5.1.21 · fixed in 5.2; From 5.2.4 · fixed in 5.3
- Linux Linux
5.3
- KernelLinux
fixed in 4.19.320; From 4.20.0 · fixed in 5.4.282; From 5.3.0 · fixed in 5.10.224; From 5.5.0 · fixed in 5.15.165; From 5.11.0 · fixed in 6.1.103; From 5.16.0 · fixed in 6.6.44; From 6.2.0 · fixed in 6.10.3
References 8
git.kernel.org
- stable/c/d81d7e347d1f1f48a5634607d39eb90c161c8afe
- stable/c/e02f9941e8c011aa3eafa799def6a134ce06bcfa
- stable/c/de2a011a13a46468a6e8259db58b1b62071fe136
- stable/c/9771e3d8365ae1dd5e8846a204cb9af14e3e656a
- stable/c/b609753cbbd38f8c0affd4956c0af178348523ac
- stable/c/c3893d9de8ee153baac56d127d844103488133b5
- stable/c/299bc6ffa57e04e74c6cce866d6c0741fb4897a1
- stable/c/f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6