CVE-2026-80644 — ocfs2: don't BUG_ON an invalid journal dinode
In the Linux kernel, the following vulnerability has been resolved: ocfs2: don't BUG_ON an invalid journal dinode [BUG] A fuzzed OCFS2 image can corrupt the current slot journal dinode while mount is still in progress. The mount path first reports the invalid journal block and then crashes in shutdown: kernel BUG at fs/ocfs2/journal.c:1034! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034 Call Trace: ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116 ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline] ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083 get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698 get_tree_bdev+0x24/0x40 fs/super.c:1721 ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184 vfs_get_tree+0x9a/0x370 fs/super.c:1758 fc_mount fs/namespace.c:1199 [inline] do_new_mount_fc fs/namespace.c:3642 [inline] do_new_mount fs/namespace.c:3718 [inline] path_mount+0x5b8/0x1ea0 fs/namespace.c:4028 do_mount fs/namespace.c:4041 [inline] __do_sys_mount fs/namespace.c:4229 [inline] __se_sys_mount fs/namespace.c:4206 [inline] __x64_sys_mount+0x282/0x320 fs/namespace.c:4206 ... [CAUSE] ocfs2_journal_toggle_dirty() used to return -EIO when journal->j_bh no longer contained a valid dinode, because the startup and shutdown paths already handled that failure. Commit 10995aa2451a ("ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.") changed the check to a BUG_ON() under the assumption that the journal dinode had already been validated. That turns an unexpected invalid journal dinode during mount teardown into a kernel crash instead of a normal mount failure. [FIX] Replace the BUG_ON() with WARN_ON() and return -EIO. This keeps the invariant warning for debugging, but restores the original behavior of failing startup or shutdown cleanly instead of panicking the kernel.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < 86509c5296fe46ad6bcdd83931a53c2c6b7913a8≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < 12c32a7350b670aaaaf2e01583d8648ec0c9755c≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < b460f8d01a12061853d02c8fb693fb42450acd7d≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < a06eec15596e5801bad59ad16cd2bf4f0fa839a1≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < 3852478d34c7baa490ba9c7374ee901a56eea577≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < 5b33f99f3e48465bd93219495381a5aef4fa967f≥ 10995aa2451afa20b721cc7de856cae1a13dba57 and < c0438198c28b1d22c272751af5e717c11d9fa8dd and 1 moreversion 2.6.29 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/12c32a7350b670aaaaf2e01583d8648ec0c9755c
- git.kernel.org/stable/c/bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0
- git.kernel.org/stable/c/86509c5296fe46ad6bcdd83931a53c2c6b7913a8
- git.kernel.org/stable/c/3852478d34c7baa490ba9c7374ee901a56eea577
- git.kernel.org/stable/c/c0438198c28b1d22c272751af5e717c11d9fa8dd
- git.kernel.org/stable/c/a06eec15596e5801bad59ad16cd2bf4f0fa839a1
- git.kernel.org/stable/c/b460f8d01a12061853d02c8fb693fb42450acd7d
- git.kernel.org/stable/c/5b33f99f3e48465bd93219495381a5aef4fa967f
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 20h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 20h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 20h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 20h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 20h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 20h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80644 is "ocfs2: don't BUG_ON an invalid journal dinode", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.