Bug 2540353 (CVE-2026-93258)

Summary: CVE-2026-93258 kernel: ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's OCFS2 (Oracle Cluster File System 2) file system. When an inode validation failure occurs during an active directory lookup, the file system improperly resets the directory inode type to a regular file. A local user can exploit this flaw by performing directory lookups on a crafted or corrupted file system, triggering a kernel assertion failure and leading to a Denial of Service (DoS).
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-09-24 16:23:53 UTC
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.