ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2142dfa1de61e25b83198af0308ec7689cca25d3, Kernel 488a5c2bf7543c3cd3f07a025f2e62be91599430, Kernel 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023 and 3 more.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <2142dfa1de61e25b83198af0308ec7689cca25d3, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <488a5c2bf7543c3cd3f07a025f2e62be91599430, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <f725b290ed79ad61e4f721fee95a287892d8b1ad, >=393d1d1d76933886d5e1ce603214c9987589c6d5 <f7e6b5548f915d7aa435d0764d41eacfb49c6e09 | 2142dfa1de61e25b83198af0308ec7689cca25d3, 488a5c2bf7543c3cd3f07a025f2e62be91599430, 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023, c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5, f725b290ed79ad61e4f721fee95a287892d8b1ad, f7e6b5548f915d7aa435d0764d41eacfb49c6e09 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket