linux-kernel - [syzbot] general protection fault in __pm_runtime

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000473c1a05da12ee25@google.com>
Date:   Sat, 12 Mar 2022 21:35:25 -0800
From:   syzbot <syzbot+b9bd12fbed3485a3e51f@...kaller.appspotmail.com>
To:     gregkh@...uxfoundation.org, len.brown@...el.com,
        linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
        pavel@....cz, rafael@...nel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] general protection fault in __pm_runtime_resume (2)

Hello,

syzbot found the following issue on:

HEAD commit:    92f90cc9fe0e Merge tag 'fuse-fixes-5.17-rc8' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=118cd3be700000
kernel config:  https://syzkaller.appspot.com/x/.config?x=442f8ac61e60a75e
dashboard link: https://syzkaller.appspot.com/bug?extid=b9bd12fbed3485a3e51f
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15b64e79700000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1652811a700000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b9bd12fbed3485a3e51f@...kaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc0000000072: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000390-0x0000000000000397]
CPU: 0 PID: 46 Comm: kworker/u5:0 Not tainted 5.17.0-rc7-syzkaller-00060-g92f90cc9fe0e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_cmd_work
RIP: 0010:__pm_runtime_resume+0x45/0x170 drivers/base/power/runtime.c:1126
Code: 44 89 ee e8 2d af 02 fd 45 85 ed 75 4e e8 a3 ab 02 fd 48 8d bd 91 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 03 01 00 00
RSP: 0018:ffffc9000116fc28 EFLAGS: 00010216
RAX: dffffc0000000000 RBX: ffff888022f8d000 RCX: 0000000000000000
RDX: 0000000000000072 RSI: ffffffff8476148d RDI: 0000000000000391
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8ffc4a0f
R10: ffffffff84761483 R11: 000000000000000a R12: 0000000000000004
R13: 0000000000000000 R14: ffff888022f8d190 R15: ffff888022f8d128
FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc3fad2418 CR3: 000000007f4c3000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 pm_runtime_get_sync include/linux/pm_runtime.h:420 [inline]
 h5_enqueue+0x175/0x390 drivers/bluetooth/hci_h5.c:632
 hci_uart_send_frame+0x1ee/0x6b0 drivers/bluetooth/hci_ldisc.c:286
 hci_send_frame+0x1c0/0x370 net/bluetooth/hci_core.c:2942
 hci_cmd_work+0x204/0x3c0 net/bluetooth/hci_core.c:3861
 process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307
 worker_thread+0x657/0x1110 kernel/workqueue.c:2454
 kthread+0x2e9/0x3a0 kernel/kthread.c:377
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__pm_runtime_resume+0x45/0x170 drivers/base/power/runtime.c:1126
Code: 44 89 ee e8 2d af 02 fd 45 85 ed 75 4e e8 a3 ab 02 fd 48 8d bd 91 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 03 01 00 00
RSP: 0018:ffffc9000116fc28 EFLAGS: 00010216
RAX: dffffc0000000000 RBX: ffff888022f8d000 RCX: 0000000000000000
RDX: 0000000000000072 RSI: ffffffff8476148d RDI: 0000000000000391
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8ffc4a0f
R10: ffffffff84761483 R11: 000000000000000a R12: 0000000000000004
R13: 0000000000000000 R14: ffff888022f8d190 R15: ffff888022f8d128
FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f989adfd718 CR3: 000000007683c000 CR4: 0000000000350ef0
----------------
Code disassembly (best guess):
   0:	44 89 ee             	mov    %r13d,%esi
   3:	e8 2d af 02 fd       	callq  0xfd02af35
   8:	45 85 ed             	test   %r13d,%r13d
   b:	75 4e                	jne    0x5b
   d:	e8 a3 ab 02 fd       	callq  0xfd02abb5
  12:	48 8d bd 91 03 00 00 	lea    0x391(%rbp),%rdi
  19:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  20:	fc ff df
  23:	48 89 fa             	mov    %rdi,%rdx
  26:	48 c1 ea 03          	shr    $0x3,%rdx
* 2a:	0f b6 04 02          	movzbl (%rdx,%rax,1),%eax <-- trapping instruction
  2e:	48 89 fa             	mov    %rdi,%rdx
  31:	83 e2 07             	and    $0x7,%edx
  34:	38 d0                	cmp    %dl,%al
  36:	7f 08                	jg     0x40
  38:	84 c0                	test   %al,%al
  3a:	0f 85 03 01 00 00    	jne    0x143


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches