==================================================================
BUG: KASAN: out-of-bounds in hidraw_ioctl+0x5e1/0xae0 drivers/hid/hidraw.c:396
Read of size 4 at addr ffff8881d24bc018 by task syz-executor.2/3677

CPU: 1 PID: 3677 Comm: syz-executor.2 Not tainted 5.3.0+ #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+0xca/0x13e lib/dump_stack.c:113
 print_address_description+0x6a/0x32c mm/kasan/report.c:351
 __kasan_report.cold+0x1a/0x33 mm/kasan/report.c:482
 kasan_report+0xe/0x12 mm/kasan/common.c:618
 hidraw_ioctl+0x5e1/0xae0 drivers/hid/hidraw.c:396
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:509 [inline]
 do_vfs_ioctl+0xd2d/0x1330 fs/ioctl.c:696
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:713
 __do_sys_ioctl fs/ioctl.c:720 [inline]
 __se_sys_ioctl fs/ioctl.c:718 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:718
 do_syscall_64+0xb7/0x580 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459a09
Code: fd b7 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 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f984a5bbc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459a09
RDX: 0000000020000580 RSI: 0000000090044802 RDI: 0000000000000005
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f984a5bc6d4
R13: 00000000004c23c4 R14: 00000000004d5a08 R15: 00000000ffffffff

Allocated by task 238:
 save_stack+0x1b/0x80 mm/kasan/common.c:69
 set_track mm/kasan/common.c:77 [inline]
 __kasan_kmalloc mm/kasan/common.c:493 [inline]
 __kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:466
 slab_post_alloc_hook mm/slab.h:520 [inline]
 slab_alloc_node mm/slub.c:2770 [inline]
 slab_alloc mm/slub.c:2778 [inline]
 kmem_cache_alloc+0xd6/0x2d0 mm/slub.c:2783
 shmem_alloc_inode+0x18/0x40 mm/shmem.c:3630
 alloc_inode+0x61/0x1e0 fs/inode.c:227
 new_inode_pseudo+0x14/0xe0 fs/inode.c:916
 new_inode+0x1b/0x40 fs/inode.c:945
 shmem_get_inode+0x84/0x7e0 mm/shmem.c:2228
 shmem_mknod+0x5a/0x1f0 mm/shmem.c:2864
 lookup_open+0x119a/0x18d0 fs/namei.c:3224
 do_last fs/namei.c:3314 [inline]
 path_openat+0x1045/0x3f50 fs/namei.c:3525
 do_filp_open+0x1a1/0x280 fs/namei.c:3555
 do_sys_open+0x3c0/0x580 fs/open.c:1089
 do_syscall_64+0xb7/0x580 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 0:
(stack is not available)

The buggy address belongs to the object at ffff8881d24bc000
 which belongs to the cache shmem_inode_cache of size 1184
The buggy address is located 24 bytes inside of
 1184-byte region [ffff8881d24bc000, ffff8881d24bc4a0)
The buggy address belongs to the page:
page:ffffea0007492f00 refcount:1 mapcount:0 mapping:ffff8881da115180 index:0x0 compound_mapcount: 0
flags: 0x200000000010200(slab|head)
raw: 0200000000010200 dead000000000100 dead000000000122 ffff8881da115180
raw: 0000000000000000 00000000800c000c 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8881d24bbf00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff8881d24bbf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8881d24bc000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                            ^
 ffff8881d24bc080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8881d24bc100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================