KASAN: out-of-bounds Write in tls_push_record (2)

11 views
Skip to first unread message

syzbot

unread,
Jan 14, 2020, 10:28:10 PM1/14/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: db5b9190 Linux 4.19.96
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=128fac21e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7a24894346f71303
dashboard link: https://syzkaller.appspot.com/bug?extid=4c62fdd55ea1d50e1426
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+4c62fd...@syzkaller.appspotmail.com

RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000246 R12: 00007fad9d1986d4
R13: 00000000004c9b28 R14: 00000000004e2d90 R15: 0000000000000007
==================================================================
BUG: KASAN: out-of-bounds in tls_fill_prepend include/net/tls.h:373 [inline]
BUG: KASAN: out-of-bounds in tls_push_record+0x102a/0x13a0
net/tls/tls_sw.c:220
Write of size 1 at addr ffff888068c98000 by task syz-executor.0/11079

CPU: 0 PID: 11079 Comm: syz-executor.0 Not tainted 4.19.96-syzkaller #0
audit: type=1800 audit(1579058822.930:220): pid=11107 uid=0 auid=4294967295
ses=4294967295 subj=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
op=collect_data cause=failed(directio) comm="syz-executor.4" name="file0"
dev="sda1" ino=16848 res=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
print_address_description.cold+0x7c/0x20d mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report mm/kasan/report.c:412 [inline]
kasan_report.cold+0x8c/0x2ba mm/kasan/report.c:396
__asan_report_store1_noabort+0x17/0x20 mm/kasan/report.c:435
tls_fill_prepend include/net/tls.h:373 [inline]
tls_push_record+0x102a/0x13a0 net/tls/tls_sw.c:220
tls_sw_push_pending_record+0x23/0x30 net/tls/tls_sw.c:257
tls_handle_open_record net/tls/tls_main.c:156 [inline]
tls_sk_proto_close+0x674/0xb80 net/tls/tls_main.c:271
IPVS: ftp: loaded support on port[0] = 21
inet_release+0xff/0x1e0 net/ipv4/af_inet.c:428
inet6_release+0x53/0x80 net/ipv6/af_inet6.c:472
__sock_release+0xce/0x2a0 net/socket.c:579
sock_close+0x1b/0x30 net/socket.c:1140
__fput+0x2dd/0x8b0 fs/file_table.c:278
____fput+0x16/0x20 fs/file_table.c:309
task_work_run+0x145/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x273/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x53d/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45af49
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fcd20e99c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: 0000000000004000 RBX: 00007fcd20e99c90 RCX: 000000000045af49
RDX: 00000000e0ffffff RSI: 00000000200005c0 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 00000000000000d8
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcd20e9a6d4
R13: 00000000004cac30 R14: 00000000004e4428 R15: 0000000000000007

The buggy address belongs to the page:
page:ffffea0001a32600 count:1 mapcount:-512 mapping:0000000000000000
index:0x0
flags: 0xfffe0000000000()
raw: 00fffe0000000000 dead000000000100 dead000000000200 0000000000000000
raw: 0000000000000000 0000000000000000 00000001fffffdff ffff888052e68d00
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff888068c97f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888068c97f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> ffff888068c98000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888068c98080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888068c98100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


---
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 14, 2020, 2:11:15 AM10/14/20
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