general protection fault in __device_attach (2)

Status: upstream: reported C repro on 2026/08/14 08:51
Subsystems: kernel
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+de42beb9ccc760a210ab@syzkaller.appspotmail.com
First crash: 17d, last: 1d00h
✨ AI Patch Versions (2)
Version Stage Reported Report Link Job
2 moderation 2026/08/14 14:50 Discussion abe77c96-ec34-4c72-9a4e-12da9bb8ce68
1 moderation 2026/08/14 09:41 Discussion 4397f1ef-be0d-4e1b-897a-fcd37e50cc6b
✨ AI Jobs (4)
ID Workflow Result Correct Bug Created Started Finished Revision
abe77c96 patch-iteration general protection fault in __device_attach (2) 2026/08/14 14:12 2026/08/14 14:12 2026/08/14 14:50 746171ee
4397f1ef patching general protection fault in __device_attach (2) 2026/08/14 08:57 2026/08/14 08:57 2026/08/14 09:41 b13552fe
59f2329e repro-c Reproduced: ✅ general protection fault in __device_attach (2) 2026/08/13 14:12 2026/08/13 14:12 2026/08/13 18:03 0165196a
7a76bdb0 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ general protection fault in __device_attach (2) 2026/07/31 00:00 2026/07/31 00:00 2026/07/31 00:48 aaffb173
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] driver core: Cancel the attach if device addition fails 1 (1) 2026/08/15 02:22
[syzbot] [kernel?] general protection fault in __device_attach (2) 1 (3) 2026/08/15 02:13
Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-54 general protection fault in __device_attach (2) 2 syz, C 5 514d 1320d 0/2 upstream: reported C repro on 2023/01/03 03:10
upstream general protection fault in __device_attach kernel 2 syz, C done done 2 978d 1615d 0/29 auto-obsoleted due to no activity on 2024/03/19 23:28
android-5-10 general protection fault in __device_attach (2) 2 syz, C error inconclusive 13 7d06h 1319d 0/2 upstream: reported C repro on 2023/01/03 15:59
android-6-1 general protection fault in __device_attach origin:upstream 2 syz, C error error 3 171d 1171d 0/2 upstream: reported C repro on 2023/06/01 06:12
linux-4.19 general protection fault in __device_attach 2 syz, C error 35 1265d 2073d 0/1 upstream: reported C repro on 2020/12/11 04:31
android-5-10 general protection fault in __device_attach 2 1 1567d 1567d 0/2 auto-closed as invalid on 2022/07/29 21:17
android-5-15 general protection fault in __device_attach origin:upstream 2 syz, C error error 7 124d 1320d 0/2 upstream: reported C repro on 2023/01/03 07:29
android-54 general protection fault in __device_attach 2 8 1758d 2014d 0/2 auto-closed as invalid on 2022/02/18 18:30
Last patch testing requests (2)
Created Duration User Patch Repo Result
2026/08/15 01:58 14m eadavis@qq.com patch upstream OK job log log
2026/08/14 08:23 13m nogikh@google.com upstream report job log log

Sample crash report:
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
serio serio2: device_add() failed for  (), error: -12
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000021: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]
CPU: 2 UID: 0 PID: 847 Comm: kworker/2:2 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: events_long serio_handle_event
RIP: 0010:__device_attach+0xb0/0x4d0 drivers/base/dd.c:1074
Code: c1 e8 03 42 80 3c 28 00 0f 85 d1 03 00 00 48 ba 00 00 00 00 00 fc ff df 4c 8b 7b 48 49 8d bf 08 01 00 00 48 89 f9 48 c1 e9 03 <0f> b6 14 11 84 d2 74 06 0f 8e 9d 03 00 00 45 0f b6 af 08 01 00 00
RSP: 0018:ffffc90004ee7b40 EFLAGS: 00010206
RAX: 1ffff110068d6a48 RBX: ffff8880346b51f8 RCX: 0000000000000021
RDX: dffffc0000000000 RSI: ffffffff8c400400 RDI: 0000000000000108
RBP: 1ffff920009dcf69 R08: 0000000000000000 R09: fffffbfff224331a
R10: ffffc90004ee7b40 R11: 0000000000000000 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff8880346b52c0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880d5fe9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdf29b81d58 CR3: 000000000e994000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 serio_find_driver drivers/input/serio/serio.c:112 [inline]
 serio_handle_event+0x60a/0x990 drivers/input/serio/serio.c:206
 process_one_work+0xa23/0x1940 kernel/workqueue.c:3322
 process_scheduled_works kernel/workqueue.c:3405 [inline]
 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__device_attach+0xb0/0x4d0 drivers/base/dd.c:1074
Code: c1 e8 03 42 80 3c 28 00 0f 85 d1 03 00 00 48 ba 00 00 00 00 00 fc ff df 4c 8b 7b 48 49 8d bf 08 01 00 00 48 89 f9 48 c1 e9 03 <0f> b6 14 11 84 d2 74 06 0f 8e 9d 03 00 00 45 0f b6 af 08 01 00 00
RSP: 0018:ffffc90004ee7b40 EFLAGS: 00010206
RAX: 1ffff110068d6a48 RBX: ffff8880346b51f8 RCX: 0000000000000021
RDX: dffffc0000000000 RSI: ffffffff8c400400 RDI: 0000000000000108
RBP: 1ffff920009dcf69 R08: 0000000000000000 R09: fffffbfff224331a
R10: ffffc90004ee7b40 R11: 0000000000000000 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff8880346b52c0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880d5fe9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdf29b81d58 CR3: 000000000e994000 CR4: 0000000000352ef0
----------------
Code disassembly (best guess):
   0:	c1 e8 03             	shr    $0x3,%eax
   3:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)
   8:	0f 85 d1 03 00 00    	jne    0x3df
   e:	48 ba 00 00 00 00 00 	movabs $0xdffffc0000000000,%rdx
  15:	fc ff df
  18:	4c 8b 7b 48          	mov    0x48(%rbx),%r15
  1c:	49 8d bf 08 01 00 00 	lea    0x108(%r15),%rdi
  23:	48 89 f9             	mov    %rdi,%rcx
  26:	48 c1 e9 03          	shr    $0x3,%rcx
* 2a:	0f b6 14 11          	movzbl (%rcx,%rdx,1),%edx <-- trapping instruction
  2e:	84 d2                	test   %dl,%dl
  30:	74 06                	je     0x38
  32:	0f 8e 9d 03 00 00    	jle    0x3d5
  38:	45 0f b6 af 08 01 00 	movzbl 0x108(%r15),%r13d
  3f:	00

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/14 08:50 upstream 2f1baf1fc892 2377cd3d .config console log report C ci-qemu-upstream general protection fault in __device_attach
2026/07/30 03:25 upstream fc46aed51f62 2377cd3d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in __device_attach
2026/07/29 02:45 upstream 3b5f4b83c4ab 19622d9d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in __device_attach
2026/07/29 01:32 upstream 3b5f4b83c4ab 19622d9d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in __device_attach
* Struck through repros no longer work on HEAD.