ip_tables: iptables: counters copy to user failed while replacing table
ubi0: attaching mtd0
ubi0: scanning is finished
==================================================================
ip_tables: iptables: counters copy to user failed while replacing table
BUG: KASAN: slab-out-of-bounds in memcpy include/linux/string.h:372 [inline]
BUG: KASAN: slab-out-of-bounds in pdu_read+0x94/0x100 net/9p/protocol.c:64
Read of size 31091 at addr ffff88805ab9222d by task syz-executor.4/13008

CPU: 1 PID: 13008 Comm: syz-executor.4 Not tainted 4.14.214-syzkaller #0
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+0x1b2/0x283 lib/dump_stack.c:58
 print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
 kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
 kasan_report+0x6f/0x7b mm/kasan/report.c:409
 memcpy+0x20/0x50 mm/kasan/kasan.c:302
 memcpy include/linux/string.h:372 [inline]
 pdu_read+0x94/0x100 net/9p/protocol.c:64
 p9pdu_vreadf net/9p/protocol.c:167 [inline]
 p9pdu_readf+0x381/0x1970 net/9p/protocol.c:540
 p9_client_version net/9p/client.c:990 [inline]
 p9_client_create+0x9b2/0x12c0 net/9p/client.c:1088
Cannot find add_set index 0 as target
ip_tables: iptables: counters copy to user failed while replacing table
 v9fs_session_init+0x1c5/0x1540 fs/9p/v9fs.c:422
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
 v9fs_mount+0x73/0x860 fs/9p/vfs_super.c:135
 mount_fs+0x92/0x2a0 fs/super.c:1237
 vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
 vfs_kern_mount fs/namespace.c:1036 [inline]
 do_new_mount fs/namespace.c:2549 [inline]
 do_mount+0xe53/0x2a00 fs/namespace.c:2879
 SYSC_mount fs/namespace.c:3095 [inline]
 SyS_mount+0xa8/0x120 fs/namespace.c:3072
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
Cannot find add_set index 0 as target
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45e219
RSP: 002b:00007fe8dfd04c68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 000000000045e219
RDX: 00000000200004c0 RSI: 0000000020000480 RDI: 0000000000000000
RBP: 000000000119bfd0 R08: 0000000020000500 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007fff0eaac98f R14: 00007fe8dfd059c0 R15: 000000000119bf8c

Allocated by task 13008:
 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]
 p9_fcall_alloc+0x19/0x90 net/9p/client.c:242
 p9_tag_alloc net/9p/client.c:312 [inline]
 p9_client_prepare_req.part.0+0x7f8/0xb60 net/9p/client.c:728
 p9_client_prepare_req net/9p/client.c:718 [inline]
 p9_client_rpc+0x170/0x1520 net/9p/client.c:763
 p9_client_version net/9p/client.c:980 [inline]
 p9_client_create+0x92f/0x12c0 net/9p/client.c:1088
 v9fs_session_init+0x1c5/0x1540 fs/9p/v9fs.c:422
 v9fs_mount+0x73/0x860 fs/9p/vfs_super.c:135
 mount_fs+0x92/0x2a0 fs/super.c:1237
 vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
 vfs_kern_mount fs/namespace.c:1036 [inline]
 do_new_mount fs/namespace.c:2549 [inline]
 do_mount+0xe53/0x2a00 fs/namespace.c:2879
 SYSC_mount fs/namespace.c:3095 [inline]
 SyS_mount+0xa8/0x120 fs/namespace.c:3072
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb

Freed by task 0:
(stack is not available)

The buggy address belongs to the object at ffff88805ab92200
 which belongs to the cache kmalloc-16384 of size 16384
The buggy address is located 45 bytes inside of
 16384-byte region [ffff88805ab92200, ffff88805ab96200)
The buggy address belongs to the page:
page:ffffea00016ae400 count:1 mapcount:0 mapping:ffff88805ab92200 index:0x0 compound_mapcount: 0
flags: 0xfff00000008100(slab|head)
raw: 00fff00000008100 ffff88805ab92200 0000000000000000 0000000100000001
raw: ffffea0001654020 ffff88813fe81c48 ffff88813fe08200 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88805ab94100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88805ab94180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88805ab94200: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc
                               ^
 ffff88805ab94280: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff88805ab94300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
ubi0: attached mtd0 (name "mtdram test device", size 0 MiB)
ubi0: PEB size: 4096 bytes (4 KiB), LEB size: 3968 bytes
ubi0: min./max. I/O unit sizes: 1/64, sub-page size 1
ubi0: VID header offset: 64 (aligned 64), data offset: 128
Cannot find add_set index 0 as target
ubi0: good PEBs: 32, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 23
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 706216527
ubi0: available PEBs: 28, total reserved PEBs: 4, PEBs reserved for bad PEB handling: 0
ubi0: background thread "ubi_bgt0d" started, PID 13050
ubi: mtd0 is already attached to ubi0