ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full() (CVE-2026-93258) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93258

ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full()

Answer in brief

CVE-2026-93258 records a Unknown severity vulnerability in ocfs2: do not use make_bad_inode() in ocfs2_read_inode_block_full(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=58b6fcd2ab34399258dc509f701d0986a8e0bcaa <0e7459abff46e28e64367057038ef8607e63f599 \|\| >=58b6fcd2ab34399258dc509f701d0986a8e0bcaa <d48ace65322001b41bb5322442a21425ef4407d4	0e7459abff46e28e64367057038ef8607e63f599, d48ace65322001b41bb5322442a21425ef4407d4
Linux/Linuxgeneric	6.19	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 0e7459abff46e28e64367057038ef8607e63f599 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.