Skip to main content

Linux Kernel EUVDEUVD-2026-81798

| CVE-2026-90205 HIGH
2026-09-17 Linux GHSA-hqp2-385x-jjhh
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious OCFS2 image with out-of-range orphan slot
  2. Delivery
    Victim mounts crafted filesystem
  3. Exploit
    Corrupt dinode enters orphan wipe/recovery
  4. Execution
    Unvalidated slot indexes osb_orphan_wipes out of bounds
  5. Persist
    OOB access / slab-UAF read
  6. Impact
    Kernel crash (denial of service)

Vulnerability Assessment

Exploitation Conditions

Requires the OCFS2 filesystem driver (fs/ocfs2) and that the victim mount and process an attacker-crafted or corrupted OCFS2 image whose dinode has OCFS2_ORPHANED_FL set with an i_orphaned_slot value outside osb->max_slots; the OOB access is reached specifically through inode wipe / orphan recovery (ocfs2_wipe_inode -> ocfs2_get_system_file_inode) during inode eviction. Limiting factors: local attack vector (no remote reach), required user interaction (UI:R - a victim must mount the malicious image), and the fact that mounting an arbitrary filesystem image normally requires CAP_SYS_ADMIN, which substantially narrows realistic exploitation to scenarios involving automatic mounting of untrusted removable media or images. Affects kernels from 2.6.16 up to the fix; patched in 6.18.52, 7.2.6, and 7.3-rc1.

Impact

This is a genuine memory-safety defect but not a high-priority exploitation target. The vendor CVSS is 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), yet the vector itself signals limited reach: AV:L means no remote access, and UI:R means a victim must mount and process a maliciously crafted OCFS2 filesystem image (mounting a filesystem typically requires CAP_SYS_ADMIN, further gating the trigger). No EPSS score, no CISA KEV listing, and no public exploit code are present in the input, so there is no evidence of active exploitation or automatable weaponization. The technical root cause - ocfs2_validate_inode_block() validates i_suballoc_slot but leaves the active ordinary orphan slot (i_orphaned_slot) unchecked, allowing an out-of-range value to index osb_orphan_wipes and the slot-local system-inode cache - produces an out-of-bounds access whose observed manifestation (KASAN slab-use-after-free read during orphan recovery / inode eviction) is a crash. The vendor-rated C:H/I:H/A:H is optimistic: the demonstrated primitive is an OOB/UAF read on a teardown path, which realistically yields denial-of-service with, at most, contingent information disclosure - full integrity impact is not established by the description. Conflict to flag: CWE is 'N/A' in the input and the 'Buffer Overflow' tag describes an OOB array-index / read condition (closer to CWE-129/CWE-125) rather than a classic write overflow.

Exploit ScenarioDerived

An attacker crafts a malicious OCFS2 disk image (or corrupts an existing one) in which a dinode carries OCFS2_ORPHANED_FL together with an i_orphaned_slot value outside the mounted filesystem's slot range. When a victim mounts the image and the kernel later processes that inode during orphan wipe/recovery, ocfs2_wipe_inode() uses the unvalidated slot to index osb_orphan_wipes and the system-inode cache out of bounds, causing a KASAN-detected slab-use-after-free and a kernel crash. No public proof-of-concept is identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 18, 2026

Out-of-bounds memory access in the Linux kernel's OCFS2 cluster filesystem can be triggered when a victim mounts and processes a crafted or corrupted OCFS2 image whose on-disk inode sets OCFS2_ORPHANED_FL with an i_orphaned_slot value outside the mounted filesystem's valid slot range, causing ocfs2_wipe_inode() to index osb_orphan_wipes out of bounds during orphan wipe and inode eviction. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H, i.e. a local, low-complexity, unauthenticated-per-vector flaw that nonetheless requires the victim to interactively mount the malicious image and, in most real deployments, to hold CAP_SYS_ADMIN to mount at all, which sharply narrows realistic exposure. Vendor patches are available in Linux 6.18.52, 7.2.6, and 7.3-rc1, and no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.

RemediationAI

Apply the vendor-released kernel patch by upgrading to Linux 6.18.52, 7.2.6, or 7.3-rc1 (or a later stable/mainline release containing the fix), which can be obtained from the upstream stable commits linked in the advisory: https://git.kernel.org/stable/c/b2d31acbd3b182755b019183fb46949ba5e39b9f, https://git.kernel.org/stable/c/c6c908f9b4edfb04534b15573168ae038f7a9cbf, and https://git.kernel.org/stable/c/3d7c4b7ce7b4baedfd8699fa692cd95f77d332de; distribution kernels should be updated once their maintainers backport these commits, and the NVD page https://nvd.nist.gov/vuln/detail/CVE-2026-90205 can be tracked for vendor advisories. If immediate patching is not possible, the most effective compensating control is to break the attack precondition rather than the code path: because exploitation requires the victim to mount an attacker-supplied OCFS2 image, disable automatic mounting of untrusted removable media and disk images (for example, turn off desktop/udisks auto-mount handling and require explicit administrative mount actions), with the trade-off that users lose plug-and-play convenience for removable storage. Where the ocfs2 driver is not required, blacklist or do not load it (e.g. 'install ocfs2 /bin/false' in modprobe configuration, or omit the module from the initramfs), which removes the vulnerable code entirely at the cost of losing OCFS2 support; if OCFS2 is needed only for inspection of untrusted images, prefer parsing them on a throwaway, network-isolated host or with a userspace/FUSE-based reader rather than a privileged kernel mount, since avoiding the privileged mount also avoids the CAP_SYS_ADMIN requirement that the attacker must convince a victim to exercise. Finally, restrict CAP_SYS_ADMIN to the smallest possible set of users and services so that ordinary accounts cannot mount arbitrary filesystem images, accepting the operational friction this adds for legitimate mount-based workflows.

Affected VersionsENISA

Linux 2.6.16
Linux patch: 7.2.6
Linux b4df6ed8db0c387d38292e31f00adc4cd297ed5a <b2d31acbd3b182755b019183fb46949ba5e39b9f
Linux patch: 7.3-rc1
Linux b4df6ed8db0c387d38292e31f00adc4cd297ed5a <3d7c4b7ce7b4baedfd8699fa692cd95f77d332de
Linux patch: 0
Linux b4df6ed8db0c387d38292e31f00adc4cd297ed5a <c6c908f9b4edfb04534b15573168ae038f7a9cbf
Linux patch: 6.18.52

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OCFS2 is a clustered, journaling, shared-disk filesystem that stores most of its metadata in a hidden system directory of inodes; a dinode marked with OCFS2_ORPHANED_FL records an orphan slot number (i_orphaned_slot) identifying which cluster node's orphan recovery structures own the pending delete, and that slot is used to index the per-mount array osb_orphan_wipes and a slot-local system-inode cache. The flaw is a classic trust boundary violation over on-disk metadata: ocfs2_validate_inode_block() verifies i_suballoc_slot (among other fields) but never bounds-checks an active i_orphaned_slot against osb->max_slots, so a corrupted or attacker-crafted dinode can carry an out-of-range slot that is later dereferenced inside ocfs2_get_system_file_inode() via ocfs2_wipe_inode() (fs/ocfs2/inode.c) during eviction/root-recovery, as demonstrated by the reported KASAN slab-use-after-free/OOB read trace (fs/ocfs2/sysfile.c:102, reached through ocfs2_recover_orphans -> ocfs2_evict_inode). The root-cause class is improper validation of untrusted input with a resulting out-of-bounds read (no CWE was supplied in the source data; the associated tags list buffer overflow), and the fix of record validates both the ordinary orphan slot used by inode wipe processing and the append-DIO orphan slot used by DIO completion and orphan recovery, rejecting corrupt metadata at the existing inode validation boundary before it reaches downstream consumers. Affected CPEs are generic Linux kernel entries (cpe:2.3:a:linux:linux), reflecting that this is core kernel code rather than a distinct product, and the code path has existed since Linux 2.6.16.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.1 HIGH

Local crafted-image trigger requiring a victim mount (AV:L/UI:R); demonstrated OOB/UAF-read primitive yields info disclosure and crash (C:H/A:H) but no established write/integrity impact (I:N).

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 18, 2026 - 18:22 NVD
7.8 (HIGH)
Patch available
Sep 17, 2026 - 17:19 EUVD
CVE Published
Sep 17, 2026 - 16:07 cve.org
HIGH 7.8
CVE Published
Sep 17, 2026 - 16:07 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: validate orphan slot during inode read

Patch series "ocfs2: validate active orphan slots during inode read".

OCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes. A corrupted slot can therefore index osb_orphan_wipes or the slot-local system-inode cache outside their allocations before the corruption is reported.

Patch 1 validates the ordinary orphan slot used by inode wipe processing. Patch 2 validates the append-DIO orphan slot used by DIO completion and orphan recovery. Both checks reject corrupt metadata at the existing inode validation boundary.

This patch (of 2):

[BUG] A corrupted dinode with OCFS2_ORPHANED_FL can carry an i_orphaned_slot outside the mounted filesystem slot range. ocfs2_wipe_inode() uses it to index osb_orphan_wipes before looking up the orphan directory, causing an out-of-bounds memory access.

BUG: KASAN: slab-use-after-free in ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 Read of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85 Call Trace: ... ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 ocfs2_wipe_inode+0x292/0xf70 fs/ocfs2/inode.c:840 ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline] ocfs2_evict_inode+0x6c9/0x1170 fs/ocfs2/inode.c:1295 evict+0x38e/0x8f0 fs/inode.c:810 iput_final fs/inode.c:1914 [inline] iput fs/inode.c:1966 [inline] iput+0x55b/0x8b0 fs/inode.c:1926 ocfs2_recover_orphans+0x610/0xe40 fs/ocfs2/journal.c:2374 ocfs2_complete_recovery+0x5af/0xd00 fs/ocfs2/journal.c:1373 ...

[CAUSE] ocfs2_validate_inode_block() validates i_suballoc_slot but leaves the active ordinary orphan slot unchecked. Downstream consumers assume that the value is smaller than osb->max_slots.

[FIX] Reject an active i_orphaned_slot outside the slot range during dinode validation, before the inode reaches orphan wipe processing.

Executive ViewAI

Why It Matters

A memory-safety flaw in the Linux kernel's OCFS2 clustered filesystem can be triggered when a user mounts a malicious or corrupted OCFS2 volume, potentially allowing kernel memory disclosure and causing system crashes or denial of service on affected hosts. Exposure is limited to systems that run OCFS2 and where an attacker can convince a privileged operator to mount an untrusted image, a scenario most relevant to shared cluster storage, virtualized/container lab environments, and forensic or image-processing workflows. Affected platform owners should treat this as a priority patching item for any OCFS2-enabled Linux fleet, while noting that no public exploit or confirmed active exploitation has been observed.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
OCFS2 is a niche Oracle clustered filesystem, rare outside specific cluster deployments
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy