ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 393d1d1d76933886d5e1ce603214c9987589c6d5 · < 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
There are many places that will get unhappy (and crash) when ext4_iget() returns a bad inode. However, if iget the boot loader inode, allows a bad inode to be returned, because the inode may not be initialized. This mechanism can be used to bypass some checks and cause panic. To solve this problem, we add a special iget flag EXT4_IGET_BAD. Only with this flag we'd be returning bad inode from ext4_iget(), otherwise we always return the error code if the inode is bad inode.(suggested by Jan Kara)
From the CVE record · Linux
The Linux kernel's ext4 inode handling can return a bad boot loader inode because that inode may be uninitialized. This can bypass checks and cause a kernel panic. The input does not specify the access or interaction needed to trigger it.
Engineers running Linux kernels with ext4 should check their systems; affected versions are not specified.