CVE-2026-93258
ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 58b6fcd2ab34399258dc509f701d0986a8e0bcaa · fixed in 0e7459abff46e28e64367057038ef8607e63f599; From 58b6fcd2ab34399258dc509f701d0986a8e0bcaa · fixed in d48ace65322001b41bb5322442a21425ef4407d4
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.6