CVE-2026-80644

CVE CVE-2026-80644EUVD EUVD-2026-67520Published 2026-08-28T06:48:55.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 10995aa2451afa20b721cc7de856cae1a13dba57 <5b33f99f3e48465bd93219495381a5aef4fa967f; patch: 0; patch: 6.6.145; 10995aa2451afa20b721cc7de856cae1a13dba57 <bf1d59cf2ac8a1730607ebaa0bc0dc6d00f197d0; 10995aa2451afa20b721cc7de856cae1a13dba57 <3852478d34c7baa490ba9c7374ee901a56eea577; patch: 7.2; patch: 5.10.261; patch: 6.18.40; patch: 6.1.178; patch: 5.15.212; 10995aa2451afa20b721cc7de856cae1a13dba57 <a06eec15596e5801bad59ad16cd2bf4f0fa839a1; 10995aa2451afa20b721cc7de856cae1a13dba57 <b460f8d01a12061853d02c8fb693fb42450acd7d; patch: 6.12.97; 2.6.29; 10995aa2451afa20b721cc7de856cae1a13dba57 <86509c5296fe46ad6bcdd83931a53c2c6b7913a8; 10995aa2451afa20b721cc7de856cae1a13dba57 <12c32a7350b670aaaaf2e01583d8648ec0c9755c; patch: 7.1.5; 10995aa2451afa20b721cc7de856cae1a13dba57 <c0438198c28b1d22c272751af5e717c11d9fa8dd

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.