[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <94eb2c05a380bd8f2a055ffc6de5@google.com>
Date: Sun, 10 Dec 2017 05:31:01 -0800
From: syzbot
<bot+afbe81311aa0da046f1e62a665eccddac254f803@...kaller.appspotmail.com>
To: davem@...emloft.net, herbert@...dor.apana.org.au,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: KASAN: wild-memory-access Write in scatterwalk_copychunks
Hello,
syzkaller hit the following crash on
b9f242047f2185f762e952d8d773f6d01f3c2d20
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers
==================================================================
BUG: KASAN: wild-memory-access in memcpy include/linux/string.h:341 [inline]
BUG: KASAN: wild-memory-access in memcpy_dir crypto/scatterwalk.c:28
[inline]
BUG: KASAN: wild-memory-access in scatterwalk_copychunks+0x206/0x480
crypto/scatterwalk.c:43
Write of size 16 at addr 0005080000000000 by task syzkaller952806/3086
CPU: 1 PID: 3086 Comm: syzkaller952806 Not tainted 4.15.0-rc2+ #142
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/0x257 lib/dump_stack.c:53
kasan_report_error mm/kasan/report.c:349 [inline]
kasan_report+0x13b/0x340 mm/kasan/report.c:409
check_memory_region_inline mm/kasan/kasan.c:260 [inline]
check_memory_region+0x137/0x190 mm/kasan/kasan.c:267
memcpy+0x37/0x50 mm/kasan/kasan.c:303
memcpy include/linux/string.h:341 [inline]
memcpy_dir crypto/scatterwalk.c:28 [inline]
scatterwalk_copychunks+0x206/0x480 crypto/scatterwalk.c:43
blkcipher_done_slow crypto/blkcipher.c:81 [inline]
blkcipher_walk_done+0xa4b/0xde0 crypto/blkcipher.c:118
glue_ctr_crypt_128bit+0x597/0xc20 arch/x86/crypto/glue_helper.c:289
ctr_crypt+0x34/0x40 arch/x86/crypto/serpent_avx2_glue.c:168
__ablk_encrypt+0x1d1/0x2d0 crypto/ablk_helper.c:64
ablk_encrypt+0x23e/0x2c0 crypto/ablk_helper.c:84
skcipher_crypt_ablkcipher crypto/skcipher.c:714 [inline]
skcipher_decrypt_ablkcipher+0x312/0x420 crypto/skcipher.c:732
crypto_skcipher_decrypt include/crypto/skcipher.h:463 [inline]
chacha_decrypt crypto/chacha20poly1305.c:152 [inline]
poly_tail_continue+0x42a/0x6b0 crypto/chacha20poly1305.c:167
poly_tail+0x40f/0x520 crypto/chacha20poly1305.c:201
poly_cipherpad+0x33e/0x470 crypto/chacha20poly1305.c:231
poly_cipher+0x303/0x440 crypto/chacha20poly1305.c:262
poly_adpad+0x347/0x480 crypto/chacha20poly1305.c:292
poly_ad+0x25c/0x300 crypto/chacha20poly1305.c:316
poly_setkey+0x2fc/0x3e0 crypto/chacha20poly1305.c:343
poly_init+0x16c/0x1d0 crypto/chacha20poly1305.c:366
poly_genkey+0x422/0x590 crypto/chacha20poly1305.c:406
chachapoly_decrypt+0x73/0x90 crypto/chacha20poly1305.c:488
crypto_aead_decrypt include/crypto/aead.h:362 [inline]
_aead_recvmsg crypto/algif_aead.c:308 [inline]
aead_recvmsg+0x14a7/0x1bc0 crypto/algif_aead.c:329
sock_recvmsg_nosec net/socket.c:805 [inline]
sock_recvmsg+0xc9/0x110 net/socket.c:812
___sys_recvmsg+0x29b/0x630 net/socket.c:2207
__sys_recvmsg+0xe2/0x210 net/socket.c:2252
SYSC_recvmsg net/socket.c:2264 [inline]
SyS_recvmsg+0x2d/0x50 net/socket.c:2259
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x43ff39
RSP: 002b:00007ffe6f979678 EFLAGS: 00000217 ORIG_RAX: 000000000000002f
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043ff39
RDX: 0000000000000000 RSI: 0000000020c0c000 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000217 R12: 00000000004018a0
R13: 0000000000401930 R14: 0000000000000000 R15: 0000000000000000
==================================================================
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.
Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>
syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
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.
View attachment "config.txt" of type "text/plain" (126531 bytes)
Download attachment "raw.log" of type "application/octet-stream" (8628 bytes)
View attachment "repro.txt" of type "text/plain" (1671 bytes)
Download attachment "repro.c" of type "application/octet-stream" (2670 bytes)
Powered by blists - more mailing lists