kernel panic: stack-protector: Kernel stack is corrupted in: ADDR

283 views
Skip to first unread message

syzbot

unread,
Feb 25, 2018, 2:59:06 PM2/25/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot hit the following crash on net-next commit
f74290fdb363665538743d14c4f00aeacdb68d87 (Sat Feb 24 05:04:20 2018 +0000)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
CC: [core...@netfilter.org da...@davemloft.net f...@strlen.de
kad...@blackhole.kfki.hu kuz...@ms2.inr.ac.ru linux-...@vger.kernel.org
net...@vger.kernel.org netfilt...@vger.kernel.org pa...@netfilter.org
yosh...@linux-ipv6.org]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+a39285...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

arp_tables: arptables: counters copy to user failed while replacing table
Dead loop on virtual device tunl0, fix it urgently!
Dead loop on virtual device tunl0, fix it urgently!
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
0000000061020920

CPU: 0 PID: 4231 Comm: syz-executor3 Not tainted 4.16.0-rc2+ #241
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x24d lib/dump_stack.c:53
panic+0x1e4/0x41c kernel/panic.c:183
__stack_chk_fail+0x22/0x30 kernel/panic.c:643
do_ipt_get_ctl+0x9bf/0xac0 net/ipv4/netfilter/ip_tables.c:1743
nf_sockopt net/netfilter/nf_sockopt.c:104 [inline]
nf_getsockopt+0x6a/0xc0 net/netfilter/nf_sockopt.c:122
ip_getsockopt+0x152/0x200 net/ipv4/ip_sockglue.c:1572
tcp_getsockopt+0x82/0xd0 net/ipv4/tcp.c:3332
sock_common_getsockopt+0x95/0xd0 net/core/sock.c:2938
SYSC_getsockopt net/socket.c:1881 [inline]
SyS_getsockopt+0x178/0x340 net/socket.c:1863
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4568ba
RSP: 002b:0000000000a3e3b8 EFLAGS: 00000202 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 0000000000a3e3e0 RCX: 00000000004568ba
RDX: 0000000000000041 RSI: 0000000000000000 RDI: 0000000000000013
RBP: 00000000006ff8a0 R08: 0000000000a3e3dc R09: 0000000000004000
R10: 0000000000a3e4e0 R11: 0000000000000202 R12: 0000000000000000
R13: 0000000000000013 R14: 0000000000000000 R15: 00000000006fdda0
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream
raw.log.txt
config.txt

Dmitry Vyukov

unread,
Jul 17, 2018, 10:21:10 AM7/17/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
Last happened 125 days ago, does not look too actionable on itself and
there was a bunch of fixed in netfilter:

#syz invalid
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/94eb2c0772a853271805660ed3f6%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages