general protection fault in ath9k_htc_txep

7 views
Skip to first unread message

syzbot

unread,
Jan 30, 2022, 5:06:17 AM1/30/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 993a44fa85c1 usb: gadget: f_uac2: allow changing interface..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=122da70fb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d7c811a1a4d0135
dashboard link: https://syzkaller.appspot.com/bug?extid=6eec4aeaddcf3f5a325f
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [da...@davemloft.net ku...@kernel.org kv...@kernel.org linux-...@vger.kernel.org linux-w...@vger.kernel.org net...@vger.kernel.org linu...@vger.kernel.org]

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

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

general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067]
CPU: 0 PID: 4731 Comm: sed Not tainted 5.17.0-rc1-syzkaller-00028-g993a44fa85c1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ath_printk+0xde/0x20e drivers/net/wireless/ath/main.c:82
Code: 40 c7 44 24 40 18 00 00 00 4c 89 74 24 20 48 89 44 24 28 0f 84 e1 00 00 00 e8 de 04 90 fb 49 8d 7c 24 10 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 74 05 e8 b6 13 bf fb 4d 8b 64 24 10 4d 85 e4 0f 84
RSP: 0018:ffffc90000007900 EFLAGS: 00010006
RAX: 000000000000000c RBX: 1ffff92000000f20 RCX: ffffc900009f9000
RDX: 0000000000040000 RSI: ffffffff85b3a022 RDI: 0000000000000060
RBP: ffffc900000079f8 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff8314f916 R11: 0000000000000000 R12: 0000000000000050
R13: ffffffff86736f80 R14: ffffffff86737020 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f83032499ee CR3: 000000010bee1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
get_htc_epid_queue drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:149 [inline]
ath9k_htc_txep+0x358/0x400 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:706
ath9k_htc_txcompletion_cb+0x1cd/0x2f0 drivers/net/wireless/ath/ath9k/htc_hst.c:348
hif_usb_regout_cb+0x115/0x1c0 drivers/net/wireless/ath/ath9k/hif_usb.c:90
__usb_hcd_giveback_urb+0x2b0/0x5c0 drivers/usb/core/hcd.c:1663
usb_hcd_giveback_urb+0x367/0x410 drivers/usb/core/hcd.c:1733
dummy_timer+0x11f9/0x32b0 drivers/usb/gadget/udc/dummy_hcd.c:1987
call_timer_fn+0x1a5/0x6b0 kernel/time/timer.c:1421
expire_timers kernel/time/timer.c:1466 [inline]
__run_timers.part.0+0x67c/0xa30 kernel/time/timer.c:1734
__run_timers kernel/time/timer.c:1715 [inline]
run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1747
__do_softirq+0x288/0x9a5 kernel/softirq.c:558
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x113/0x170 kernel/softirq.c:637
irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
sysvec_apic_timer_interrupt+0x8e/0xc0 arch/x86/kernel/apic/apic.c:1097
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:check_kcov_mode+0xf/0x40 kernel/kcov.c:166
Code: 7c 24 08 e8 b3 13 2f 00 e9 61 fd ff ff cc cc cc cc cc cc cc cc cc cc cc cc cc cc 65 8b 05 a9 ce be 7e 89 c2 81 e2 00 01 00 00 <a9> 00 01 ff 00 74 10 31 c0 85 d2 74 15 8b 96 bc 14 00 00 85 d2 74
RSP: 0018:ffffc90008b8f8a0 EFLAGS: 00000246
RAX: 0000000080000000 RBX: dffffc0000000000 RCX: 00007fff6dc9e000
RDX: 0000000000000000 RSI: ffff88810a8e3800 RDI: 0000000000000003
RBP: ffff888119dc3020 R08: 00007fff6dcbf000 R09: ffff888131eabf7b
R10: ffffffff81668831 R11: 0000000000000001 R12: 00007fff6dc9e000
R13: ffff888119dc3000 R14: ffff888119dc3008 R15: 00007fff6dcbf000
write_comp_data kernel/kcov.c:221 [inline]
__sanitizer_cov_trace_cmp8+0x1d/0x70 kernel/kcov.c:267
browse_rb mm/mmap.c:352 [inline]
validate_mm+0x421/0x800 mm/mmap.c:424
mmap_region+0xc84/0x14e0 mm/mmap.c:1846
do_mmap+0x869/0xfb0 mm/mmap.c:1582
vm_mmap_pgoff+0x1b7/0x280 mm/util.c:519
vm_mmap+0x92/0xc0 mm/util.c:538
elf_map+0x229/0x2a0 fs/binfmt_elf.c:392
load_elf_binary+0xca0/0x4a50 fs/binfmt_elf.c:1154
search_binary_handler fs/exec.c:1727 [inline]
exec_binprm fs/exec.c:1768 [inline]
bprm_execve fs/exec.c:1837 [inline]
bprm_execve+0x7ef/0x19a0 fs/exec.c:1799
do_execveat_common+0x5e3/0x780 fs/exec.c:1926
do_execve fs/exec.c:1994 [inline]
__do_sys_execve fs/exec.c:2070 [inline]
__se_sys_execve fs/exec.c:2065 [inline]
__x64_sys_execve+0x8f/0xc0 fs/exec.c:2065
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f8303196337
Code: Unable to access opcode bytes at RIP 0x7f830319630d.
RSP: 002b:00007fff3ee0c868 EFLAGS: 00000246 ORIG_RAX: 000000000000003b
RAX: ffffffffffffffda RBX: 00007f8303a7ae28 RCX: 00007f8303196337
RDX: 00007f8303a7ae50 RSI: 00007f8303a7ae28 RDI: 00007f8303a7aee0
RBP: 00007f8303a7aee0 R08: 00007f8303a7aee5 R09: 00007f8303388000
R10: 00007f830302c800 R11: 0000000000000246 R12: 00007f8303a7ae50
R13: 00007f830333bff4 R14: 00007f8303a7ae50 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ath_printk+0xde/0x20e drivers/net/wireless/ath/main.c:82
Code: 40 c7 44 24 40 18 00 00 00 4c 89 74 24 20 48 89 44 24 28 0f 84 e1 00 00 00 e8 de 04 90 fb 49 8d 7c 24 10 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 74 05 e8 b6 13 bf fb 4d 8b 64 24 10 4d 85 e4 0f 84
RSP: 0018:ffffc90000007900 EFLAGS: 00010006
RAX: 000000000000000c RBX: 1ffff92000000f20 RCX: ffffc900009f9000
RDX: 0000000000040000 RSI: ffffffff85b3a022 RDI: 0000000000000060
RBP: ffffc900000079f8 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff8314f916 R11: 0000000000000000 R12: 0000000000000050
R13: ffffffff86736f80 R14: ffffffff86737020 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f830319630d CR3: 000000010bee1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 40 c7 44 24 40 18 00 rex movl $0x18,0x40(%rsp)
7: 00 00
9: 4c 89 74 24 20 mov %r14,0x20(%rsp)
e: 48 89 44 24 28 mov %rax,0x28(%rsp)
13: 0f 84 e1 00 00 00 je 0xfa
19: e8 de 04 90 fb callq 0xfb9004fc
1e: 49 8d 7c 24 10 lea 0x10(%r12),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 05 je 0x36
31: e8 b6 13 bf fb callq 0xfbbf13ec
36: 4d 8b 64 24 10 mov 0x10(%r12),%r12
3b: 4d 85 e4 test %r12,%r12
3e: 0f .byte 0xf
3f: 84 .byte 0x84


---
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.

syzbot

unread,
Apr 27, 2022, 2:59:24 PM4/27/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages