KASAN: use-after-free Write in pcrypt_aead_enc

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cc24401 Linux 4.14.229
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11380931d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=51785e7f450b788d
dashboard link: https://syzkaller.appspot.com/bug?extid=f0c426bf1ad62725f6e3

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f0c426...@syzkaller.appspotmail.com

audit: type=1804 audit(1617831633.955:138): pid=7411 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir977926108/syzkaller.E66VuM/258/bus" dev="sda1" ino=15747 res=1
TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters.
==================================================================
BUG: KASAN: use-after-free in pcrypt_aead_enc+0xc4/0xf0 crypto/pcrypt.c:142
Write of size 4 at addr ffff8880156405f0 by task kworker/0:0/3

CPU: 0 PID: 3 Comm: kworker/0:0 Not tainted 4.14.229-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: pencrypt padata_parallel_worker
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x191 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_store4_noabort+0x68/0x70 mm/kasan/report.c:434
pcrypt_aead_enc+0xc4/0xf0 crypto/pcrypt.c:142
padata_parallel_worker+0x202/0x2e0 kernel/padata.c:87
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
IPv6: ADDRCONF(NETDEV_CHANGE): gtp36: link becomes ready
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

Allocated by task 7411:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
__do_kmalloc mm/slab.c:3720 [inline]
__kmalloc+0x15a/0x400 mm/slab.c:3729
kmalloc include/linux/slab.h:493 [inline]
kzalloc include/linux/slab.h:661 [inline]
tls_push_record+0xfa/0x1270 net/tls/tls_sw.c:250
tls_push_pending_closed_record net/tls/tls_main.c:205 [inline]
tls_push_pending_closed_record+0xbc/0xf0 net/tls/tls_main.c:198
tls_complete_pending_work include/net/tls.h:159 [inline]
tls_sw_sendpage+0x7f8/0xb50 net/tls/tls_sw.c:563
inet_sendpage+0x155/0x590 net/ipv4/af_inet.c:779
kernel_sendpage net/socket.c:3407 [inline]
sock_sendpage+0xdf/0x140 net/socket.c:871
pipe_to_sendpage+0x226/0x2d0 fs/splice.c:451
splice_from_pipe_feed fs/splice.c:502 [inline]
__splice_from_pipe+0x326/0x7a0 fs/splice.c:626
splice_from_pipe fs/splice.c:661 [inline]
generic_splice_sendpage+0xc1/0x110 fs/splice.c:832
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x115/0x160 fs/splice.c:1018
splice_direct_to_actor+0x27c/0x730 fs/splice.c:973
do_splice_direct+0x164/0x210 fs/splice.c:1061
do_sendfile+0x47f/0xb30 fs/read_write.c:1441
SYSC_sendfile64 fs/read_write.c:1502 [inline]
SyS_sendfile64+0xff/0x110 fs/read_write.c:1488
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb

Freed by task 7411:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xc9/0x250 mm/slab.c:3815
tls_push_record+0xc3b/0x1270 net/tls/tls_sw.c:293
tls_push_pending_closed_record net/tls/tls_main.c:205 [inline]
tls_push_pending_closed_record+0xbc/0xf0 net/tls/tls_main.c:198
tls_complete_pending_work include/net/tls.h:159 [inline]
tls_sw_sendpage+0x7f8/0xb50 net/tls/tls_sw.c:563
inet_sendpage+0x155/0x590 net/ipv4/af_inet.c:779
kernel_sendpage net/socket.c:3407 [inline]
sock_sendpage+0xdf/0x140 net/socket.c:871
pipe_to_sendpage+0x226/0x2d0 fs/splice.c:451
splice_from_pipe_feed fs/splice.c:502 [inline]
__splice_from_pipe+0x326/0x7a0 fs/splice.c:626
splice_from_pipe fs/splice.c:661 [inline]
generic_splice_sendpage+0xc1/0x110 fs/splice.c:832
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x115/0x160 fs/splice.c:1018
splice_direct_to_actor+0x27c/0x730 fs/splice.c:973
do_splice_direct+0x164/0x210 fs/splice.c:1061
do_sendfile+0x47f/0xb30 fs/read_write.c:1441
SYSC_sendfile64 fs/read_write.c:1502 [inline]
SyS_sendfile64+0xff/0x110 fs/read_write.c:1488
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb

The buggy address belongs to the object at ffff888015640580
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 112 bytes inside of
512-byte region [ffff888015640580, ffff888015640780)
The buggy address belongs to the page:
page:ffffea0000559000 count:1 mapcount:0 mapping:ffff888015640080 index:0x0
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffff888015640080 0000000000000000 0000000100000006
raw: ffffea000295e6e0 ffffea00023e4a60 ffff88813fe80940 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff888015640480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888015640500: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff888015640580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888015640600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888015640680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.