ext4: make sure the first directory block is not a hole
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4e19d6b65fb4fc42e352ce9883649e049da14743 · < c3893d9de8ee153baac56d127d844103488133b5| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's ext4 filesystem may accept a non-inline directory whose first block is a hole, leaving it without the expected '.' and '..' entries. Code that relies on those entries may crash when it processes the corrupted directory. The input does not establish whether an attacker can trigger this remotely or what access is required.
Engineers running Linux kernels with ext4 should check their kernel versions; affected versions are not specified.