ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
This reverts commit 58b6fcd2ab34 ("ocfs2: mark inode bad upon validation failure during read").
Since 'make_bad_inode()' resets inode type to S_IFREG, doing this for directory inode during active VFS lookup is likely to confuse the latter, including VFS_BUG_ON_INODE() triggered in this case.
From the CVE record · Linux
The ocfs2 filesystem can mark a directory inode as a regular file after inode validation fails during a read. During an active VFS lookup, this can confuse the VFS and trigger VFS_BUG_ON_INODE(). The input does not specify attacker access or interaction requirements.
Engineers running Linux kernels with ocfs2 should check their versions; no affected versions are specified.