general protection fault in __ext4_journal_get_write_access (6)

Status: upstream: reported on 2026/11/18 12:32
Reported-by: syzbot+ba7989e532b5d68db3f9@syzkaller.appspotmail.com
First crash: 4d10h, last: 4d10h
▶ ▼ Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 general protection fault in __ext4_journal_get_write_access (2) 2 1 655d 655d 0/3 auto-obsoleted due to no activity on 2025/05/16 06:11
upstream general protection fault in __ext4_journal_get_write_access fuse ext4 2 syz, C done done 7 2203d 2252d 22/29 fixed on 2022/11/15 22:34
linux-6.1 general protection fault in __ext4_journal_get_write_access 2 2 798d 801d 0/3 auto-obsoleted due to no activity on 2024/12/24 15:34
linux-6.1 general protection fault in __ext4_journal_get_write_access (5) 2 1 260d 260d 0/3 auto-obsoleted due to no activity on 2026/06/15 01:27
android-6-1 general protection fault in __ext4_journal_get_write_access missing-backport origin:lts 2 syz, C error 107 20d 412d 0/2 upstream: reported C repro on 2025/10/06 16:02
linux-6.1 general protection fault in __ext4_journal_get_write_access (3) 2 1 489d 489d 0/3 auto-obsoleted due to no activity on 2025/10/29 07:49
linux-6.1 BUG: unable to handle kernel paging request in __ext4_journal_get_write_access 8 syz error 2 145d 159d 0/3 auto-obsoleted due to no activity on 2026/10/16 04:45
linux-6.1 general protection fault in __ext4_journal_get_write_access (4) 2 1 361d 361d 0/3 auto-obsoleted due to no activity on 2026/03/06 15:43

Sample crash report:
EXT4-fs error (device loop0): ext4_validate_block_bitmap:429: comm ext4lazyinit: bg 0: block 5: invalid block bitmap
general protection fault, probably for non-canonical address 0xdffffc0000000007: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
CPU: 1 PID: 7028 Comm: ext4lazyinit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
RIP: 0010:__ext4_journal_get_write_access+0xc3/0x6e0 fs/ext4/ext4_jbd2.c:231
Code: 31 c0 49 8d 5e 30 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 8b 68 b4 ff 48 8b 1b 48 83 c3 38 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 6e 68 b4 ff 4c 8b 23 4d 85 e4 4c
RSP: 0018:ffffc90004a87bc0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: d165bcd58f5b2400
RDX: ffff88802b11a23c RSI: ffffffff8aac2e40 RDI: ffffffff8afe72a0
RBP: ffffc90004a87c90 R08: ffff88804e4551d0 R09: 0000000000000001
R10: dffffc0000000000 R11: ffffed1009c87a19 R12: ffff888077fd6028
R13: dffffc0000000000 R14: ffff88804e4551d0 R15: 1ffff92000950f80
FS:  0000000000000000(0000) GS:ffff8880b8d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa4cf594000 CR3: 000000002a4fe000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ext4_init_inode_table+0x3bc/0x7b0 fs/ext4/ialloc.c:1607
 ext4_run_li_request fs/ext4/super.c:3749 [inline]
 ext4_lazyinit_thread+0xb92/0x17b0 fs/ext4/super.c:3840
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__ext4_journal_get_write_access+0xc3/0x6e0 fs/ext4/ext4_jbd2.c:231
Code: 31 c0 49 8d 5e 30 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 8b 68 b4 ff 48 8b 1b 48 83 c3 38 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 6e 68 b4 ff 4c 8b 23 4d 85 e4 4c
RSP: 0018:ffffc90004a87bc0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: d165bcd58f5b2400
RDX: ffff88802b11a23c RSI: ffffffff8aac2e40 RDI: ffffffff8afe72a0
RBP: ffffc90004a87c90 R08: ffff88804e4551d0 R09: 0000000000000001
R10: dffffc0000000000 R11: ffffed1009c87a19 R12: ffff888077fd6028
R13: dffffc0000000000 R14: ffff88804e4551d0 R15: 1ffff92000950f80
FS:  0000000000000000(0000) GS:ffff8880b8d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d46a8dde38 CR3: 0000000066c35000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	31 c0                	xor    %eax,%eax
   2:	49 8d 5e 30          	lea    0x30(%r14),%rbx
   6:	48 89 d8             	mov    %rbx,%rax
   9:	48 c1 e8 03          	shr    $0x3,%rax
   d:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)
  12:	74 08                	je     0x1c
  14:	48 89 df             	mov    %rbx,%rdi
  17:	e8 8b 68 b4 ff       	call   0xffb468a7
  1c:	48 8b 1b             	mov    (%rbx),%rbx
  1f:	48 83 c3 38          	add    $0x38,%rbx
  23:	48 89 d8             	mov    %rbx,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1) <-- trapping instruction
  2f:	74 08                	je     0x39
  31:	48 89 df             	mov    %rbx,%rdi
  34:	e8 6e 68 b4 ff       	call   0xffb468a7
  39:	4c 8b 23             	mov    (%rbx),%r12
  3c:	4d 85 e4             	test   %r12,%r12
  3f:	4c                   	rex.WR

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/18 12:31 linux-6.1.y c75b0cf0982c eb4895d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan general protection fault in __ext4_journal_get_write_access
2026/11/18 12:39 linux-6.1.y c75b0cf0982c eb4895d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in __ext4_journal_get_write_access
* Struck through repros no longer work on HEAD.