CVE-2026-93258: ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: do not use makebadinode() in ocfs2readinodeblockfull()
This reverts commit 58b6fcd2ab34 ("ocfs2: mark inode bad upon validation failure during read").
Since 'makebadinode()' resets inode type to SIFREG, doing this for directory inode during active VFS lookup is likely to confuse the latter, including VFSBUGONINODE() triggered in this case.
Affected Software
Event History
Frequently Asked Questions
Which deployments are most relevant to triage?
The issue is relevant to Linux systems using the OCFS2 filesystem. The described failure involves a directory inode during an active VFS lookup after inode-block validation fails.
Are fixed Linux kernel versions identified?
No specific kernel release versions are provided. The supplied references identify two stable kernel commits containing the resolution.
Is a remote attack vector or attacker prerequisite documented?
No. The available information does not specify an attack vector, required privileges, or whether specially crafted filesystem contents are required.