[v5.15] general protection fault in h5_recv

3 views
Skip to first unread message

syzbot

unread,
Jun 4, 2025, 2:57:29 AM6/4/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 98f47d0e9b8c Linux 5.15.184
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=134bbc82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d966a9f787a9782
dashboard link: https://syzkaller.appspot.com/bug?extid=847d690a94ced3d5b66f
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e51314fa9b0/disk-98f47d0e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3348ed80ea4e/vmlinux-98f47d0e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3e02a814f2cc/bzImage-98f47d0e.xz

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

general protection fault, probably for non-canonical address 0xdffffc000000005f: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000002f8-0x00000000000002ff]
CPU: 1 PID: 4426 Comm: syz.3.36 Not tainted 5.15.184-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:h5_recv+0x149/0x8b0 drivers/bluetooth/hci_h5.c:569
Code: 89 54 24 70 48 89 4c 24 28 48 c1 e9 03 48 89 4c 24 30 48 89 44 24 38 48 c1 e8 03 48 89 44 24 68 4c 89 74 24 18 48 8b 44 24 40 <80> 3c 18 00 74 08 4c 89 f7 e8 e9 d4 ba fa 4d 8b 36 31 ff 4c 89 f6
RSP: 0000:ffffc90003affc40 EFLAGS: 00010202
RAX: 000000000000005f RBX: dffffc0000000000 RCX: 000000000000005e
RDX: 1ffff1100c32dd02 RSI: 000000000000005f RDI: 0000000000000000
RBP: ffffc90003affd80 R08: dffffc0000000000 R09: ffffed100c32dd04
R10: ffffed100c32dd04 R11: 1ffff1100c32dd03 R12: 0000000000000001
R13: ffff88806196e800 R14: 00000000000002f8 R15: 0000000000000061
FS: 00007f06b55896c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f77002e7000 CR3: 000000005f055000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hci_uart_tty_receive+0x188/0x210 drivers/bluetooth/hci_ldisc.c:621
tiocsti+0x1f6/0x280 drivers/tty/tty_io.c:2312
tty_ioctl+0x3a7/0xc20 drivers/tty/tty_io.c:2724
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f06b7721969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f06b5589038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f06b7948fa0 RCX: 00007f06b7721969
RDX: 0000200000000100 RSI: 0000000000005412 RDI: 000000000000000c
RBP: 00007f06b77a3ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f06b7948fa0 R15: 00007ffe26e6c6b8
</TASK>
Modules linked in:
---[ end trace b5095e422aab4d27 ]---
RIP: 0010:h5_recv+0x149/0x8b0 drivers/bluetooth/hci_h5.c:569
Code: 89 54 24 70 48 89 4c 24 28 48 c1 e9 03 48 89 4c 24 30 48 89 44 24 38 48 c1 e8 03 48 89 44 24 68 4c 89 74 24 18 48 8b 44 24 40 <80> 3c 18 00 74 08 4c 89 f7 e8 e9 d4 ba fa 4d 8b 36 31 ff 4c 89 f6
RSP: 0000:ffffc90003affc40 EFLAGS: 00010202
RAX: 000000000000005f RBX: dffffc0000000000 RCX: 000000000000005e
RDX: 1ffff1100c32dd02 RSI: 000000000000005f RDI: 0000000000000000
RBP: ffffc90003affd80 R08: dffffc0000000000 R09: ffffed100c32dd04
R10: ffffed100c32dd04 R11: 1ffff1100c32dd03 R12: 0000000000000001
R13: ffff88806196e800 R14: 00000000000002f8 R15: 0000000000000061
FS: 00007f06b55896c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30708ff8 CR3: 000000005f055000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 89 54 24 70 mov %edx,0x70(%rsp)
4: 48 89 4c 24 28 mov %rcx,0x28(%rsp)
9: 48 c1 e9 03 shr $0x3,%rcx
d: 48 89 4c 24 30 mov %rcx,0x30(%rsp)
12: 48 89 44 24 38 mov %rax,0x38(%rsp)
17: 48 c1 e8 03 shr $0x3,%rax
1b: 48 89 44 24 68 mov %rax,0x68(%rsp)
20: 4c 89 74 24 18 mov %r14,0x18(%rsp)
25: 48 8b 44 24 40 mov 0x40(%rsp),%rax
* 2a: 80 3c 18 00 cmpb $0x0,(%rax,%rbx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 4c 89 f7 mov %r14,%rdi
33: e8 e9 d4 ba fa call 0xfabad521
38: 4d 8b 36 mov (%r14),%r14
3b: 31 ff xor %edi,%edi
3d: 4c 89 f6 mov %r14,%rsi


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jul 25, 2025, 4:53:30 PM7/25/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=122e50a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=847d690a94ced3d5b66f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=105d08a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10cd54f0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Unable to handle kernel paging request at virtual address dfff80000000005f
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
[dfff80000000005f] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4180 Comm: syz.0.21 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : h5_recv+0x11c/0x818 drivers/bluetooth/hci_h5.c:569
lr : h5_recv+0xc4/0x818 drivers/bluetooth/hci_h5.c:566
sp : ffff80001fd07a80
x29: ffff80001fd07b70 x28: 0000000000000308 x27: 0000000000000004
x26: dfff800000000000 x25: ffff0000d8a5f800 x24: dfff800000000000
x23: 00000000000002e8 x22: 00000000000002f8 x21: ffff80001fd07c40
x20: 0000000000000001 x19: 000000000000005f x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082bf708 x15: 0000000080045440
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000061 x9 : 1fffe0001b14bf02
x8 : 000000000000005e x7 : ffff80000e694ae0 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
h5_recv+0x11c/0x818 drivers/bluetooth/hci_h5.c:-1
hci_uart_tty_receive+0x140/0x1d4 drivers/bluetooth/hci_ldisc.c:621
tiocsti+0x260/0x304 drivers/tty/tty_io.c:2312
tty_ioctl+0x384/0xde0 drivers/tty/tty_io.c:2724
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: f9001fe9 d343fd29 f90023e8 f9001be9 (387a6a68)
---[ end trace 1317db6e3fe0fa8d ]---
----------------
Code disassembly (best guess):
0: f9001fe9 str x9, [sp, #56]
4: d343fd29 lsr x9, x9, #3
8: f90023e8 str x8, [sp, #64]
c: f9001be9 str x9, [sp, #48]
* 10: 387a6a68 ldrb w8, [x19, x26] <-- trapping instruction


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages