Look up another CVE · open CVE-2026-90205 in the interactive tracker
CVE-2026-90205
ocfs2: validate orphan slot during inode read
Published 2026-09-17 (31 days ago) by the Linux kernel CNA. Subsystem fs/ocfs2. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-90205 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/ocfs2/inode.c
- What this is
- ORACLE CLUSTER FILESYSTEM 2 (OCFS2)MAINTAINERS section matched on fs/ocfs2/ · ocfs2-devel@lists.linux.dev · Supported
- Kernel module
- ocfs2
Check it on the machine
grep -w CONFIG_OCFS2_FS /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w ocfs2Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_OCFS2_FS
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-17 (31 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 7.0% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- fs/ocfs2
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.16 | 6.18.52 | c6c908f9b4ed |
| 2.6.16 | 7.2.6 | 3d7c4b7ce7b4 |
| 2.6.16 | 7.3 | b2d31acbd3b1 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The attacker-controlled field is dinode i_orphaned_slot, read from the mounted block device in ocfs2_validate_inode_block()/ocfs2_read_locked_inode() and consumed by ocfs2_wipe_inode(); it is not a field of an o2net, NFS, or SMB message. Delivery is a locally mounted OCFS2 image (loop or other block device).
- AC:LAttack complexity, low
- A crafted dinode with OCFS2_ORPHANED_FL and an attacker-chosen i_orphaned_slot is accepted before the fix. ocfs2_fill_super() calls ocfs2_complete_mount_recovery(), which queues ocfs2_recover_orphans(); that igets the orphan and iputs it into ocfs2_evict_inode()→ocfs2_wipe_inode() with no race.
- PR:NPrivileges required, none
- ocfs2_fs_type.fs_flags has no FS_USERNS_MOUNT, so only a privileged mount(2) via ocfs2_get_tree()/ocfs2_fill_super() reaches recovery. The attacker who supplies the image needs no host credentials; unlink cannot plant this value because ocfs2_orphan_add() writes osb->slot_num.
- UI:RUser interaction, required
- The bug fires from ocfs2_complete_recovery()→ocfs2_recover_orphans() after the victim mounts the crafted volume through ocfs2_fill_super(). That mount is the required user action and cannot be treated as a standing export of already-on-disk metadata.
- S:UScope, unchanged
- The out-of-bounds accesses in ocfs2_check_orphan_recovery_state() and get_local_system_inode() corrupt memory in the kernel that mounted the OCFS2 volume. No KVM, Xen, or IOMMU boundary is crossed.
- C:HConfidentiality impact, high
- get_local_system_inode() computes index = i_orphaned_slot * NUM_LOCAL_SYSTEM_INODES and reads an 8-byte inode pointer past the kcalloc'd local_system_inodes array (KASAN UAF read in ocfs2_get_system_file_inode). A non-NULL value is passed to igrab(), disclosing adjacent slab contents.
- I:HIntegrity impact, high
- ocfs2_check_orphan_recovery_state() does osb->osb_orphan_wipes[slot]++ with the untrusted i_orphaned_slot against a kcalloc(max_slots) array (max_slots ≤ 255), a heap out-of-bounds increment. The OOB pointer is then used as an inode in inode_lock/ocfs2_inode_lock.
- A:HAvailability impact, high
- ocfs2_node_map_test_bit() BUG()s when i_orphaned_slot >= OCFS2_NODE_MAP_MAX_NODES (256). Smaller out-of-range slots still OOB-index osb_orphan_wipes[] and local_system_inodes[], which KASAN reported as slab-use-after-free during ocfs2_recover_orphans() in ocfs2_complete_recovery().