CVE-2026-93258ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 58b6fcd2ab34399258dc509f701d0986a8e0bcaa builds before 0e7459abff46e28e64367057038ef8607e63f599; from 58b6fcd2ab34399258dc509f701d0986a8e0bcaa before d48ace65322001b41bb5322442a21425ef4407d4 | CNA record |
References
- https://git.kernel.org/stable/c/0e7459abff46e28e64367057038ef8607e63f599
- https://git.kernel.org/stable/c/d48ace65322001b41bb5322442a21425ef4407d4
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.