CVE-2026-80644: ocfs2: don't BUG_ON an invalid journal dinode
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 12c32a7350b670aaaaf2e01583d8648ec0c9755c, 3852478d34c7baa490ba9c7374ee901a56eea577, 5b33f99f3e48465bd93219495381a5aef4fa967f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12c32a7350b670aaaaf2e01583d8648ec0c9755c, 3852478d34c7baa490ba9c7374ee901a56eea577, 5b33f99f3e48465bd93219495381a5aef4fa967f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.29affected
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0affected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before 86509c5296fe46ad6bcdd83931a53c2c6b7913a8affected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before 12c32a7350b670aaaaf2e01583d8648ec0c9755caffected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before b460f8d01a12061853d02c8fb693fb42450acd7daffected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before a06eec15596e5801bad59ad16cd2bf4f0fa839a1affected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before 3852478d34c7baa490ba9c7374ee901a56eea577affected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before 5b33f99f3e48465bd93219495381a5aef4fa967faffected · git
- 10995aa2451afa20b721cc7de856cae1a13dba57 and later · before c0438198c28b1d22c272751af5e717c11d9fa8ddaffected · git
- before 2.6.29not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80641Aug 28, 2026 · wifi: wlcore: enable the right set of ciphers0Monitor
- ← EarlierCVE-2026-80642Aug 28, 2026 · liveupdate: Reference count incoming FLB data0Monitor
- Later →CVE-2026-80645Aug 28, 2026 · rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc()32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12c32a7350b670aaaaf2e01583d8648ec0c9755c | Vendor (CNA) |
| Linux Linux | 3852478d34c7baa490ba9c7374ee901a56eea577 | Vendor (CNA) |
| Linux Linux | 5b33f99f3e48465bd93219495381a5aef4fa967f | Vendor (CNA) |
| Linux Linux | 86509c5296fe46ad6bcdd83931a53c2c6b7913a8 | Vendor (CNA) |
| Linux Linux | a06eec15596e5801bad59ad16cd2bf4f0fa839a1 | Vendor (CNA) |
| Linux Linux | b460f8d01a12061853d02c8fb693fb42450acd7d | Vendor (CNA) |
| Linux Linux | bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0 | Vendor (CNA) |
| Linux Linux | c0438198c28b1d22c272751af5e717c11d9fa8dd | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3852478d34c7baa490ba9c7374ee901a56eea577
- git.kernel.org/stable/c/5b33f99f3e48465bd93219495381a5aef4fa967f
- git.kernel.org/stable/c/86509c5296fe46ad6bcdd83931a53c2c6b7913a8
- git.kernel.org/stable/c/a06eec15596e5801bad59ad16cd2bf4f0fa839a1
- git.kernel.org/stable/c/b460f8d01a12061853d02c8fb693fb42450acd7d
- git.kernel.org/stable/c/bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0
- git.kernel.org/stable/c/c0438198c28b1d22c272751af5e717c11d9fa8dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.