BUG: unable to handle kernel paging request in blk_mq_complete_request_remote

Status: upstream: reported on 2026/09/22 23:16
Reported-by: syzbot+f7dc1c307e0649592270@syzkaller.appspotmail.com
First crash: 9d07h, last: 9d07h
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: unable to handle kernel paging request in blk_mq_complete_request_remote prio:high block 8 46 1d03h 35d 0/29 upstream: reported on 2026/08/27 10:07

Sample crash report:
nvme 0000:00:02.0: enabling device (0000 -> 0002)
nvme nvme0: Removing after probe failure status: -19
Unable to handle kernel paging request at virtual address dfff800000000031
KASAN: null-ptr-deref in range [0x0000000000000188-0x000000000000018f]
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
[dfff800000000031] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5362 Comm: kworker/u4:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026
Workqueue: nvme-reset-wq nvme_reset_work
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : blk_mq_complete_request_remote+0x78/0x61c block/blk-mq.c:1210
lr : blk_mq_complete_request_remote+0x2c/0x61c block/blk-mq.c:1202
sp : ffff8000216b7560
x29: ffff8000216b7560 x28: 1fffe00019f3a478 x27: 0000000000000002
x26: ffff0000d02aa480 x25: ffff0000cf9d23ea x24: dfff800000000000
x23: dfff800000000000 x22: ffff0000cf9f9728 x21: 1fffe0001a0554b6
x20: 000000000000018e x19: ffff0000d02aa480 x18: 1fffe00033e6db7e
x17: ffff8000153bd000 x16: ffff800011bb65f8 x15: ffff800018508000
x14: 0000000000000001 x13: 1fffe00019e17e49 x12: 0000000000000000
x11: ff0080000a7c749c x10: 0000000000000000 x9 : 1fffe0001a055492
x8 : 0000000000000031 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000008 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000d02aa480
Call trace:
 blk_mq_complete_request_remote+0x78/0x61c block/blk-mq.c:1210
 nvme_try_complete_req drivers/nvme/host/nvme.h:708 [inline]
 nvme_handle_cqe drivers/nvme/host/pci.c:1085 [inline]
 nvme_poll_cq+0x518/0xf50 drivers/nvme/host/pci.c:1115
 nvme_reap_pending_cqes drivers/nvme/host/pci.c:1562 [inline]
 nvme_dev_disable+0x350/0x5ec drivers/nvme/host/pci.c:2769
 nvme_remove_dead_ctrl drivers/nvme/host/pci.c:2864 [inline]
 nvme_reset_work+0x3808/0x477c drivers/nvme/host/pci.c:3015
 process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292
 worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439
 kthread+0x254/0x2e0 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: 9784bafd f9400288 91063914 d343fe88 (38f76908) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	9784bafd 	bl	0xfffffffffe12ebf4
   4:	f9400288 	ldr	x8, [x20]
   8:	91063914 	add	x20, x8, #0x18e
   c:	d343fe88 	lsr	x8, x20, #3
* 10:	38f76908 	ldrsb	w8, [x8, x23] <-- trapping instruction

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/22 23:16 linux-6.1.y 1a8763b93150 5207b90e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in blk_mq_complete_request_remote
* Struck through repros no longer work on HEAD.