BUG: unable to handle kernel paging request in dev_hard_start_xmit

10 views
Skip to first unread message

syzbot

unread,
Jun 20, 2019, 9:17:07 PM6/20/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 9f31eb60 Linux 4.19.53
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174d9c69a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7a36b9832db62b25
dashboard link: https://syzkaller.appspot.com/bug?extid=a4f84141161e90b78123
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

protocol 88fb is buggy, dev hsr_slave_0
protocol 88fb is buggy, dev hsr_slave_0
kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
kobject: 'loop5' (00000000ea619e75): kobject_uevent_env
BUG: unable to handle kernel paging request at ffff888052020ff0
PGD b001067 P4D b001067 PUD 9b17e063 PMD 5c206063 PTE 8000000052020163
Oops: 0011 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 27369 Comm: syz-executor.3 Not tainted 4.19.53+ #25
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
kobject: 'loop5' (00000000ea619e75): fill_kobj_path: path
= '/devices/virtual/block/loop5'
RIP: 0010:0xffff888052020ff0
Code: 00 00 03 00 00 00 00 00 00 00 10 89 5c 89 80 88 ff ff d0 c3 b2 95 80
88 ff ff e0 ec 70 94 80 88 ff ff e0 ec 70 94 80 88 ff ff <f0> 0f 02 52 80
88 ff ff f0 0f 02 52 80 88 ff ff 00 10 02 52 80 88
RSP: 0018:ffff8880ae8078f0 EFLAGS: 00010246
RAX: 1ffff110117dc68a RBX: ffff888052020ff0 RCX: ffff88805a494480
RDX: ffff888052020fe0 RSI: ffff88805a494480 RDI: ffff88808bee3440
RBP: ffff8880ae807968 R08: ffff88808ebe01c0 R09: ffffed1015d00f0d
R10: ffffed1015d00f0c R11: 0000000000000003 R12: dffffc0000000000
R13: ffff888052020fe0 R14: ffff88805a494480 R15: ffff88808bee3440
FS: 00007fa638373700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888052020ff0 CR3: 00000000a55a0000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
xmit_one net/core/dev.c:3253 [inline]
dev_hard_start_xmit+0xa7/0x980 net/core/dev.c:3273
__dev_queue_xmit+0x2705/0x3010 net/core/dev.c:3843
dev_queue_xmit+0x18/0x20 net/core/dev.c:3876
hsr_xmit net/hsr/hsr_forward.c:237 [inline]
hsr_forward_do net/hsr/hsr_forward.c:295 [inline]
hsr_forward_skb+0xd2e/0x1c10 net/hsr/hsr_forward.c:373
send_hsr_supervision_frame+0x8c8/0xf30 net/hsr/hsr_device.c:319
hsr_announce+0x12f/0x3b0 net/hsr/hsr_device.c:348
call_timer_fn+0x18d/0x720 kernel/time/timer.c:1326
expire_timers kernel/time/timer.c:1363 [inline]
__run_timers kernel/time/timer.c:1682 [inline]
__run_timers kernel/time/timer.c:1650 [inline]
run_timer_softirq+0x652/0x1700 kernel/time/timer.c:1695
__do_softirq+0x25c/0x921 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x180/0x1d0 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x13b/0x550 arch/x86/kernel/apic/apic.c:1056
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:869
</IRQ>
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:788
[inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160
[inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x95/0xe0
kernel/locking/spinlock.c:184
Code: 48 c7 c0 48 36 72 88 48 ba 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c
10 00 75 39 48 83 3d 0a c8 82 01 00 74 24 48 89 df 57 9d <0f> 1f 44 00 00
bf 01 00 00 00 e8 1c ca 59 fa 65 8b 05 75 7f 12 79
RSP: 0018:ffff88805c787050 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff10e46c9 RBX: 0000000000000286 RCX: 1ffff11011d7c14c
RDX: dffffc0000000000 RSI: ffff88808ebe0a68 RDI: 0000000000000286
RBP: ffff88805c787060 R08: ffff88808ebe01c0 R09: ffff88808ebe0a60
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff8879fa40
R13: 0000000000000000 R14: ffffffff8879fb00 R15: ffffffff8879fa40
rcu_read_unlock_special+0x679/0xea0 kernel/rcu/tree_plugin.h:587
__rcu_read_unlock+0x161/0x170 kernel/rcu/tree_plugin.h:428
rcu_read_unlock include/linux/rcupdate.h:680 [inline]
is_bpf_text_address+0xb6/0x170 kernel/bpf/core.c:549
kernel_text_address+0x73/0xf0 kernel/extable.c:152
__kernel_text_address+0xd/0x40 kernel/extable.c:107
unwind_get_return_address arch/x86/kernel/unwind_frame.c:18 [inline]
unwind_get_return_address+0x61/0xa0 arch/x86/kernel/unwind_frame.c:13
__save_stack_trace+0x99/0x100 arch/x86/kernel/stacktrace.c:45
save_stack_trace+0x1a/0x20 arch/x86/kernel/stacktrace.c:60
save_stack+0x45/0xd0 mm/kasan/kasan.c:448
set_track mm/kasan/kasan.c:460 [inline]
kasan_kmalloc mm/kasan/kasan.c:553 [inline]
kasan_kmalloc+0xce/0xf0 mm/kasan/kasan.c:531
kasan_slab_alloc+0xf/0x20 mm/kasan/kasan.c:490
kmem_cache_alloc+0x12e/0x700 mm/slab.c:3559
kmem_cache_zalloc include/linux/slab.h:699 [inline]
inode_alloc_security security/selinux/hooks.c:255 [inline]
selinux_inode_alloc_security+0xb6/0x2a0 security/selinux/hooks.c:3007
security_inode_alloc+0x8a/0xd0 security/security.c:448
inode_init_always+0x56e/0xb40 fs/inode.c:168
alloc_inode+0x81/0x190 fs/inode.c:217
new_inode_pseudo+0x19/0xf0 fs/inode.c:903
new_inode+0x1f/0x40 fs/inode.c:932
proc_pid_make_inode+0x22/0x230 fs/proc/base.c:1735
proc_pident_instantiate+0x82/0x2a0 fs/proc/base.c:2431
proc_pident_lookup+0x1c4/0x230 fs/proc/base.c:2469
proc_tgid_base_lookup+0x2a/0x30 fs/proc/base.c:3026
__lookup_slow+0x279/0x500 fs/namei.c:1671
lookup_slow+0x58/0x80 fs/namei.c:1688
walk_component+0x747/0x2000 fs/namei.c:1810
link_path_walk.part.0+0x980/0x1330 fs/namei.c:2141
link_path_walk fs/namei.c:2072 [inline]
path_openat+0x1f9/0x4690 fs/namei.c:3533
do_filp_open+0x1a1/0x280 fs/namei.c:3564
do_sys_open+0x3fe/0x550 fs/open.c:1069
__do_sys_open fs/open.c:1087 [inline]
__se_sys_open fs/open.c:1082 [inline]
__x64_sys_open+0x7e/0xc0 fs/open.c:1082
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4131b1
Code: 75 14 b8 02 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 19 00 00 c3 48
83 ec 08 e8 0a fa ff ff 48 89 04 24 b8 02 00 00 00 0f 05 <48> 8b 3c 24 48
89 c2 e8 53 fa ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007fa638372bb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00000000004131b1
RDX: 00007fa638372be3 RSI: 0000000000000002 RDI: 00007fa638372bd0
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000013
R10: 0000000000000008 R11: 0000000000000293 R12: 00007fa6383736d4
R13: 00000000004c86c8 R14: 00000000004deff0 R15: 00000000ffffffff
Modules linked in:
CR2: ffff888052020ff0
---[ end trace d10d695b4349324a ]---
RIP: 0010:0xffff888052020ff0
Code: 00 00 03 00 00 00 00 00 00 00 10 89 5c 89 80 88 ff ff d0 c3 b2 95 80
88 ff ff e0 ec 70 94 80 88 ff ff e0 ec 70 94 80 88 ff ff <f0> 0f 02 52 80
88 ff ff f0 0f 02 52 80 88 ff ff 00 10 02 52 80 88
RSP: 0018:ffff8880ae8078f0 EFLAGS: 00010246
RAX: 1ffff110117dc68a RBX: ffff888052020ff0 RCX: ffff88805a494480
RDX: ffff888052020fe0 RSI: ffff88805a494480 RDI: ffff88808bee3440
RBP: ffff8880ae807968 R08: ffff88808ebe01c0 R09: ffffed1015d00f0d
R10: ffffed1015d00f0c R11: 0000000000000003 R12: dffffc0000000000
R13: ffff888052020fe0 R14: ffff88805a494480 R15: ffff88808bee3440
FS: 00007fa638373700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888052020ff0 CR3: 00000000a55a0000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Oct 25, 2019, 4:50:06 AM10/25/19
to syzkaller...@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