{"id":"CVE-2025-68337","title":"jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere's issue when file system corrupted:\n------------[ cut here ]------------\nkernel…","severity":"high","cvss":7.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 470decc613ab2048b619a01028072d932d9086ee < 71bbe06c40fc59b5b15661eca8ff307f4176d7f9","Linux >= 470decc613ab2048b619a01028072d932d9086ee < ed62fd8c15d41c4127ad16b8219b63124f5962bc","Linux >= 470decc613ab2048b619a01028072d932d9086ee < 3faac6531d4818cd6be45e5bbf32937bbbc795c0","Linux >= 470decc613ab2048b619a01028072d932d9086ee < b4f8eabf6d991bd41fabcdf9302c4b3eab590cf4","Linux >= 470decc613ab2048b619a01028072d932d9086ee < a2a7f854d154a3e9232fec80782dad951655f52f","Linux >= 470decc613ab2048b619a01028072d932d9086ee < bf34c72337e40c4670cceeb79b353356933a254b","Linux >= 470decc613ab2048b619a01028072d932d9086ee < aa1703f3f706ea0867fb1991dcac709c9ec94cfb","Linux >= 470decc613ab2048b619a01028072d932d9086ee < 986835bf4d11032bba4ab8414d18fce038c61bb4","Linux 2.6.19"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-06-16T16:56:17.316148Z"},"published":"2025-12-22","updated":"2026-09-08","sourceUpdated":"2026-09-08T08:43:12.944Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-68337","references":[{"url":"https://git.kernel.org/stable/c/71bbe06c40fc59b5b15661eca8ff307f4176d7f9"},{"url":"https://git.kernel.org/stable/c/ed62fd8c15d41c4127ad16b8219b63124f5962bc"},{"url":"https://git.kernel.org/stable/c/3faac6531d4818cd6be45e5bbf32937bbbc795c0"},{"url":"https://git.kernel.org/stable/c/b4f8eabf6d991bd41fabcdf9302c4b3eab590cf4"},{"url":"https://git.kernel.org/stable/c/a2a7f854d154a3e9232fec80782dad951655f52f"},{"url":"https://git.kernel.org/stable/c/bf34c72337e40c4670cceeb79b353356933a254b"},{"url":"https://git.kernel.org/stable/c/aa1703f3f706ea0867fb1991dcac709c9ec94cfb"},{"url":"https://git.kernel.org/stable/c/986835bf4d11032bba4ab8414d18fce038c61bb4"}],"tags":["cve.org"],"epss":0.00537,"epssPercentile":0.44003,"ingestedAt":"2026-09-08T15:33:26.996Z","slug":"CVE-2025-68337","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere's issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n <TASK>\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.\n\n## Affected\n\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < 71bbe06c40fc59b5b15661eca8ff307f4176d7f9`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < ed62fd8c15d41c4127ad16b8219b63124f5962bc`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < 3faac6531d4818cd6be45e5bbf32937bbbc795c0`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < b4f8eabf6d991bd41fabcdf9302c4b3eab590cf4`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < a2a7f854d154a3e9232fec80782dad951655f52f`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < bf34c72337e40c4670cceeb79b353356933a254b`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < aa1703f3f706ea0867fb1991dcac709c9ec94cfb`\n- `Linux >= 470decc613ab2048b619a01028072d932d9086ee < 986835bf4d11032bba4ab8414d18fce038c61bb4`\n- `Linux 2.6.19`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}