BUG: unable to handle kernel paging request in trace_event_raw_event_nvme_sq

Status: moderation: reported on 2026/09/15 11:43
Subsystems: nvme
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+3b1e06f40c5c8709a288@syzkaller.appspotmail.com
First crash: 25d, last: 5d19h
▶ ▼ ✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
5d11488a repro-c 💥 BUG: unable to handle kernel paging request in trace_event_raw_event_nvme_sq 2026/09/15 14:12 2026/09/15 14:12 2026/09/15 16:47 2daa4bb5
5afdb09d assessment-security DenialOfService: ✅ Exploitable: ✅ FilesystemTrigger: ❌ NetworkTrigger: ✅ PeripheralTrigger: ✅ RemoteTrigger: ✅ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ✅ ❓ BUG: unable to handle kernel paging request in trace_event_raw_event_nvme_sq 2026/09/13 00:00 2026/09/13 00:00 2026/09/13 00:06 70a60e12

Sample crash report:
nvme 0000:00:02.0: enabling device (0000 -> 0002)
nvme nvme0: Disabling device after reset failure: -19
Unable to handle kernel paging request at virtual address dfff800000000043
KASAN: null-ptr-deref in range [0x0000000000000218-0x000000000000021f]
Mem abort info:
  ESR = 0x0000000096000005
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x05: level 1 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
  CM = 0, WnR = 0, TnD = 0, TagAccess = 0
  GCS = 0, Overlay = 0, DirtyBit = 0
[dfff800000000043] address between user and kernel address ranges
Internal error: Oops: 0000000096000005 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 5484 Comm: kworker/u8:20 Tainted: G             L      syzkaller #0 PREEMPT 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026
Workqueue: nvme-reset-wq nvme_reset_work
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : nvme_req_qid drivers/nvme/host/nvme.h:283 [inline]
pc : do_trace_event_raw_event_nvme_sq drivers/nvme/host/trace.h:154 [inline]
pc : trace_event_raw_event_nvme_sq+0x220/0x434 drivers/nvme/host/trace.h:141
lr : nvme_req_qid drivers/nvme/host/nvme.h:283 [inline]
lr : do_trace_event_raw_event_nvme_sq drivers/nvme/host/trace.h:154 [inline]
lr : trace_event_raw_event_nvme_sq+0x1fc/0x434 drivers/nvme/host/trace.h:141
sp : ffff80009a3e7860
x29: ffff80009a3e7930 x28: ffff80009a3e7880 x27: 1fffe0001b30f001
x26: dfff800000000000 x25: ffff70001347cf10 x24: ffff0000c7b2b7b0
x23: ffff0000f348c3b8 x22: 000000000000021c x21: 00000000000001a3
x20: 1fffe0001930b340 x19: ffff0000d9878008 x18: 1fffe00035bd9428
x17: 0000000000000003 x16: ffff800088a57000 x15: ffff800088b077e0
x14: 00000000001ef366 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: ffff60001e69187d x9 : 0000000000000000
x8 : 0000000000000043 x7 : 0000000000000000 x6 : 00316e30656d766e
x5 : ffff0000f348c3e4 x4 : ffff0000c7b3302c x3 : ffff8000827a4ca0
x2 : 0000000000000020 x1 : ffff0000d9878000 x0 : 0000000000000000
Call trace:
 nvme_req_qid drivers/nvme/host/nvme.h:283 [inline] (P)
 do_trace_event_raw_event_nvme_sq drivers/nvme/host/trace.h:154 [inline] (P)
 trace_event_raw_event_nvme_sq+0x220/0x434 drivers/nvme/host/trace.h:141 (P)
 __traceiter_nvme_sq+0x88/0xe0 drivers/nvme/host/trace.h:141
 __do_trace_nvme_sq drivers/nvme/host/trace.h:141 [inline]
 trace_nvme_sq drivers/nvme/host/trace.h:141 [inline]
 nvme_handle_cqe drivers/nvme/host/pci.c:1600 [inline]
 nvme_poll_cq+0xd78/0xfd8 drivers/nvme/host/pci.c:1632
 nvme_reap_pending_cqes drivers/nvme/host/pci.c:2090 [inline]
 nvme_dev_disable+0x384/0x540 drivers/nvme/host/pci.c:3344
 nvme_reset_work+0x510/0x69c drivers/nvme/host/pci.c:3506
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0x91c/0x1250 kernel/workqueue.c:3479
 worker_thread+0x798/0xbd0 kernel/workqueue.c:3560
 kthread+0x304/0x3d4 kernel/kthread.c:436
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:854
Code: 978f8a5b f94002c8 91087116 d343fec8 (38fa6908) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	978f8a5b 	bl	0xfffffffffe3e296c
   4:	f94002c8 	ldr	x8, [x22]
   8:	91087116 	add	x22, x8, #0x21c
   c:	d343fec8 	lsr	x8, x22, #3
* 10:	38fa6908 	ldrsb	w8, [x8, x26] <-- trapping instruction

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/01 04:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e8e60d3ddd25 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in trace_event_raw_event_nvme_sq
2026/09/11 11:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 5445d6419962 b6a5eeb7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in trace_event_raw_event_nvme_sq
* Struck through repros no longer work on HEAD.