WARNING: can't dereference registers at ADDR for ip apic_timer_interrupt

4 views
Skip to first unread message

syzbot

unread,
Apr 10, 2019, 12:14:08 PM4/10/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 4ed22187 Revert "ANDROID: Revert "arm64: move ELF_ET_DYN_B..
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=144834a3400000
kernel config: https://syzkaller.appspot.com/x/.config?x=7acec4778e485bac
dashboard link: https://syzkaller.appspot.com/bug?extid=40f5857aa71d2bb9197a
compiler: gcc (GCC) 8.0.1 20180413 (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+40f585...@syzkaller.appspotmail.com

WARNING: can't dereference registers at ffffffff97656f09 for ip
apic_timer_interrupt+0x84/0x90 arch/x86/entry/entry_64.S:787
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1105 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1122 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1163 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1176 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1186 comm=syz-executor1
selinux_nlmsg_perm: 6 callbacks suppressed
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1286 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1358 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1370 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1401 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1424 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1440 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1453 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1494 comm=syz-executor1
==================================================================
BUG: KASAN: stack-out-of-bounds in deref_stack_regs
arch/x86/kernel/unwind_orc.c:290 [inline]
BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1595/0x1930
arch/x86/kernel/unwind_orc.c:420
Read of size 8 at addr ffff8801d9107668 by task syz-executor1/1494

CPU: 0 PID: 1494 Comm: syz-executor1 Not tainted 4.14.78+ #26
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x11b lib/dump_stack.c:53
print_address_description+0x60/0x22b mm/kasan/report.c:252
kasan_report_error mm/kasan/report.c:351 [inline]
kasan_report.cold.6+0x11b/0x2dd mm/kasan/report.c:409
deref_stack_regs arch/x86/kernel/unwind_orc.c:290 [inline]
unwind_next_frame+0x1595/0x1930 arch/x86/kernel/unwind_orc.c:420
perf_callchain_kernel+0x39c/0x540 arch/x86/events/core.c:2354
get_perf_callchain+0x2eb/0x760 kernel/events/callchain.c:217
perf_callchain+0x14a/0x190 kernel/events/callchain.c:190
perf_prepare_sample+0x704/0x13c0 kernel/events/core.c:6140
__perf_event_output kernel/events/core.c:6256 [inline]
perf_event_output_forward+0xeb/0x230 kernel/events/core.c:6274
__perf_event_overflow+0x116/0x320 kernel/events/core.c:7510
perf_swevent_overflow+0x166/0x1f0 kernel/events/core.c:7586
perf_swevent_event+0x19c/0x270 kernel/events/core.c:7619
perf_tp_event+0x5e5/0x790 kernel/events/core.c:8048
perf_trace_run_bpf_submit+0x10f/0x170 kernel/events/core.c:8018
perf_trace_lock+0x2f6/0x4c0 include/trace/events/lock.h:39
trace_lock_release include/trace/events/lock.h:58 [inline]
lock_release+0x4dc/0x720 kernel/locking/lockdep.c:4009
rcu_lock_release include/linux/rcupdate.h:249 [inline]
rcu_read_unlock include/linux/rcupdate.h:687 [inline]
__is_insn_slot_addr+0x139/0x1f0 kernel/kprobes.c:301
is_kprobe_optinsn_slot include/linux/kprobes.h:344 [inline]
kernel_text_address+0x7c/0x120 kernel/extable.c:148
__kernel_text_address+0x9/0x30 kernel/extable.c:105
unwind_get_return_address+0x51/0x90 arch/x86/kernel/unwind_orc.c:238
__save_stack_trace+0x8d/0xf0 arch/x86/kernel/stacktrace.c:45
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc.part.1+0x4f/0xd0 mm/kasan/kasan.c:551
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=513
sclass=netlink_route_socket pig=1503 comm=syz-executor1
slab_post_alloc_hook mm/slab.h:442 [inline]
slab_alloc_node mm/slub.c:2723 [inline]
slab_alloc mm/slub.c:2731 [inline]
kmem_cache_alloc+0xe4/0x2b0 mm/slub.c:2736
kmem_cache_zalloc include/linux/slab.h:651 [inline]
ebitmap_cpy+0xc4/0x260 security/selinux/ss/ebitmap.c:60
mls_context_cpy security/selinux/ss/context.h:51 [inline]
mls_compute_sid+0x24a/0xda0 security/selinux/ss/mls.c:556
security_compute_sid.part.6+0x76f/0x1080
security/selinux/ss/services.c:1725
security_compute_sid security/selinux/ss/services.c:1764 [inline]
security_transition_sid+0xcb/0x120 security/selinux/ss/services.c:1764
socket_sockcreate_sid security/selinux/hooks.c:4344 [inline]
selinux_socket_post_create+0x4e9/0x690 security/selinux/hooks.c:4395
security_socket_post_create+0x8c/0xc0 security/security.c:1347
__sock_create+0x498/0x600 net/socket.c:1290
sock_create net/socket.c:1314 [inline]
SYSC_socket net/socket.c:1344 [inline]
SyS_socket+0xdf/0x1d0 net/socket.c:1324
do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x457569
RSP: 002b:00007f2e8762dc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
RDX: 0000000000000000 RSI: 0020000000080003 RDI: 0000000000000010
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2e8762e6d4
R13: 00000000004c4618 R14: 00000000004d78b0 R15: 00000000ffffffff

The buggy address belongs to the page:
page:ffffea00076441c0 count:0 mapcount:0 mapping: (null) index:0x0
flags: 0x4000000000000000()
raw: 4000000000000000 0000000000000000 0000000000000000 00000000ffffffff
raw: 0000000000000000 dead000000000200 0000000000000000 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8801d9107500: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1
ffff8801d9107580: f1 04 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 00
> ffff8801d9107600: 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 04
^
ffff8801d9107680: f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8801d9107700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
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,
Jun 25, 2019, 11:56:04 PM6/25/19
to syzkaller-a...@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