From: syzbot <syzbot+6ff38b320aa51ebe17e6@syzkaller.appspotmail.com>
To: daniel.vetter@ffwll.ch, ghalat@redhat.com,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, nico@fluxnic.net, sam@ravnborg.org,
syzkaller-bugs@googlegroups.com, textshell@uchuujin.de
Subject: Re: KASAN: user-memory-access Read in insert_char
Date: Tue, 10 Dec 2019 10:00:10 -0800 [thread overview]
Message-ID: <00000000000074253b05995d48bf@google.com> (raw)
In-Reply-To: <00000000000024db4105995c23cd@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 6794862a Merge tag 'for-5.5-rc1-kconfig-tag' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=158d1282e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
dashboard link: https://syzkaller.appspot.com/bug?extid=6ff38b320aa51ebe17e6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=169de77ae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=116dd1bce00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+6ff38b320aa51ebe17e6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: user-memory-access in memmove include/linux/string.h:395
[inline]
BUG: KASAN: user-memory-access in scr_memmovew include/linux/vt_buffer.h:68
[inline]
BUG: KASAN: user-memory-access in insert_char+0x206/0x400
drivers/tty/vt/vt.c:839
Read of size 212 at addr 00000000ffffff3a by task syz-executor463/9049
CPU: 0 PID: 9049 Comm: syz-executor463 Not tainted 5.5.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x197/0x210 lib/dump_stack.c:118
__kasan_report.cold+0x5/0x41 mm/kasan/report.c:510
kasan_report+0x12/0x20 mm/kasan/common.c:639
check_memory_region_inline mm/kasan/generic.c:185 [inline]
check_memory_region+0x134/0x1a0 mm/kasan/generic.c:192
memmove+0x24/0x50 mm/kasan/common.c:116
memmove include/linux/string.h:395 [inline]
scr_memmovew include/linux/vt_buffer.h:68 [inline]
insert_char+0x206/0x400 drivers/tty/vt/vt.c:839
csi_at drivers/tty/vt/vt.c:1964 [inline]
do_con_trol+0x41a6/0x61b0 drivers/tty/vt/vt.c:2431
do_con_write.part.0+0xfd9/0x1ef0 drivers/tty/vt/vt.c:2797
do_con_write drivers/tty/vt/vt.c:2565 [inline]
con_write+0x46/0xd0 drivers/tty/vt/vt.c:3135
process_output_block drivers/tty/n_tty.c:595 [inline]
n_tty_write+0x40e/0x1080 drivers/tty/n_tty.c:2333
do_tty_write drivers/tty/tty_io.c:962 [inline]
tty_write+0x496/0x7f0 drivers/tty/tty_io.c:1046
__vfs_write+0x8a/0x110 fs/read_write.c:494
vfs_write+0x268/0x5d0 fs/read_write.c:558
ksys_write+0x14f/0x290 fs/read_write.c:611
__do_sys_write fs/read_write.c:623 [inline]
__se_sys_write fs/read_write.c:620 [inline]
__x64_sys_write+0x73/0xb0 fs/read_write.c:620
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4404f9
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 0f 83 5b 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffd81600d98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 00000000004404f9
RDX: 0000000000000078 RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000401de0
R13: 0000000000401e70 R14: 0000000000000000 R15: 0000000000000000
==================================================================
prev parent reply other threads:[~2019-12-10 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 16:38 KASAN: user-memory-access Read in insert_char syzbot
2019-12-10 18:00 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000074253b05995d48bf@google.com \
--to=syzbot+6ff38b320aa51ebe17e6@syzkaller.appspotmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=sam@ravnborg.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=textshell@uchuujin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.