From: syzbot <syzbot+0165480d4ef07360eeda@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: KASAN: use-after-free Write in xfrm_hash_rebuild
Date: Thu, 16 May 2019 03:35:06 -0700 [thread overview]
Message-ID: <000000000000d028b30588fed102@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 601e6bcc Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1534f3d0a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4005028a9d5ddac8
dashboard link: https://syzkaller.appspot.com/bug?extid=0165480d4ef07360eeda
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+0165480d4ef07360eeda@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in __write_once_size
include/linux/compiler.h:220 [inline]
BUG: KASAN: use-after-free in __hlist_del include/linux/list.h:713 [inline]
BUG: KASAN: use-after-free in hlist_del_rcu include/linux/rculist.h:455
[inline]
BUG: KASAN: use-after-free in xfrm_hash_rebuild+0xfff/0x10f0
net/xfrm/xfrm_policy.c:1317
Write of size 8 at addr ffff888098529100 by task kworker/0:0/5
CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.1.0+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: events xfrm_hash_rebuild
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
print_address_description.cold+0x7c/0x20d mm/kasan/report.c:188
__kasan_report.cold+0x1b/0x40 mm/kasan/report.c:317
kasan_report+0x12/0x20 mm/kasan/common.c:614
__asan_report_store8_noabort+0x17/0x20 mm/kasan/generic_report.c:137
__write_once_size include/linux/compiler.h:220 [inline]
__hlist_del include/linux/list.h:713 [inline]
hlist_del_rcu include/linux/rculist.h:455 [inline]
xfrm_hash_rebuild+0xfff/0x10f0 net/xfrm/xfrm_policy.c:1317
process_one_work+0x98e/0x1790 kernel/workqueue.c:2268
worker_thread+0x98/0xe40 kernel/workqueue.c:2414
kthread+0x357/0x430 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Allocated by task 8152:
save_stack+0x23/0x90 mm/kasan/common.c:71
set_track mm/kasan/common.c:79 [inline]
__kasan_kmalloc mm/kasan/common.c:489 [inline]
__kasan_kmalloc.constprop.0+0xcf/0xe0 mm/kasan/common.c:462
kasan_kmalloc+0x9/0x10 mm/kasan/common.c:503
kmem_cache_alloc_node_trace+0x153/0x720 mm/slab.c:3630
kmalloc_node include/linux/slab.h:585 [inline]
kzalloc_node include/linux/slab.h:753 [inline]
__get_vm_area_node+0x12b/0x3a0 mm/vmalloc.c:1401
__vmalloc_node_range+0xd4/0x790 mm/vmalloc.c:1840
__vmalloc_node mm/vmalloc.c:1900 [inline]
__vmalloc_node_flags mm/vmalloc.c:1914 [inline]
vzalloc+0x6b/0x90 mm/vmalloc.c:1959
alloc_counters.isra.0+0x53/0x690 net/ipv6/netfilter/ip6_tables.c:819
copy_entries_to_user net/ipv4/netfilter/arp_tables.c:674 [inline]
get_entries net/ipv4/netfilter/arp_tables.c:861 [inline]
do_arpt_get_ctl+0x4a0/0x820 net/ipv4/netfilter/arp_tables.c:1482
nf_sockopt net/netfilter/nf_sockopt.c:104 [inline]
nf_getsockopt+0x80/0xe0 net/netfilter/nf_sockopt.c:122
ip_getsockopt net/ipv4/ip_sockglue.c:1574 [inline]
ip_getsockopt+0x176/0x1d0 net/ipv4/ip_sockglue.c:1554
tcp_getsockopt net/ipv4/tcp.c:3623 [inline]
tcp_getsockopt+0x95/0xf0 net/ipv4/tcp.c:3617
sock_common_getsockopt+0x9a/0xe0 net/core/sock.c:3089
__sys_getsockopt+0x168/0x250 net/socket.c:2115
__do_sys_getsockopt net/socket.c:2126 [inline]
__se_sys_getsockopt net/socket.c:2123 [inline]
__x64_sys_getsockopt+0xbe/0x150 net/socket.c:2123
do_syscall_64+0x103/0x670 arch/x86/entry/common.c:298
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 8152:
save_stack+0x23/0x90 mm/kasan/common.c:71
set_track mm/kasan/common.c:79 [inline]
__kasan_slab_free+0x102/0x150 mm/kasan/common.c:451
kasan_slab_free+0xe/0x10 mm/kasan/common.c:459
__cache_free mm/slab.c:3463 [inline]
kfree+0xcf/0x230 mm/slab.c:3786
__vunmap+0x704/0x9c0 mm/vmalloc.c:1617
__vfree+0x41/0xd0 mm/vmalloc.c:1658
vfree+0x5f/0x90 mm/vmalloc.c:1688
copy_entries_to_user net/ipv4/netfilter/arp_tables.c:706 [inline]
get_entries net/ipv4/netfilter/arp_tables.c:861 [inline]
do_arpt_get_ctl+0x67b/0x820 net/ipv4/netfilter/arp_tables.c:1482
nf_sockopt net/netfilter/nf_sockopt.c:104 [inline]
nf_getsockopt+0x80/0xe0 net/netfilter/nf_sockopt.c:122
ip_getsockopt net/ipv4/ip_sockglue.c:1574 [inline]
ip_getsockopt+0x176/0x1d0 net/ipv4/ip_sockglue.c:1554
tcp_getsockopt net/ipv4/tcp.c:3623 [inline]
tcp_getsockopt+0x95/0xf0 net/ipv4/tcp.c:3617
sock_common_getsockopt+0x9a/0xe0 net/core/sock.c:3089
__sys_getsockopt+0x168/0x250 net/socket.c:2115
__do_sys_getsockopt net/socket.c:2126 [inline]
__se_sys_getsockopt net/socket.c:2123 [inline]
__x64_sys_getsockopt+0xbe/0x150 net/socket.c:2123
do_syscall_64+0x103/0x670 arch/x86/entry/common.c:298
entry_SYSCALL_64_after_hwframe+0x49/0xbe
The buggy address belongs to the object at ffff888098529100
which belongs to the cache kmalloc-64 of size 64
The buggy address is located 0 bytes inside of
64-byte region [ffff888098529100, ffff888098529140)
The buggy address belongs to the page:
page:ffffea0002614a40 count:1 mapcount:0 mapping:ffff8880aa400340
index:0xffff888098529600
flags: 0x1fffc0000000200(slab)
raw: 01fffc0000000200 ffffea0002a22fc8 ffffea00026d2888 ffff8880aa400340
raw: ffff888098529600 ffff888098529000 000000010000001b 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888098529000: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
ffff888098529080: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
> ffff888098529100: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
^
ffff888098529180: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
ffff888098529200: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
==================================================================
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2019-05-16 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 10:35 syzbot [this message]
2019-06-27 3:59 ` KASAN: use-after-free Write in xfrm_hash_rebuild syzbot
2019-07-02 6:43 ` Dmitry Vyukov
2019-06-29 21:11 ` syzbot
2019-07-01 11:46 ` Florian Westphal
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=000000000000d028b30588fed102@google.com \
--to=syzbot+0165480d4ef07360eeda@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).