================================================================== BUG: KASAN: use-after-free in ext4_xattr_set_entry+0x13e2/0x1ed6 fs/ext4/xattr.c:1750 Write of size 4117 at addr ffffffe009e9a3e8 by task syz-executor.1/4068 CPU: 0 PID: 4068 Comm: syz-executor.1 Not tainted 5.15.0-rc1-syzkaller-00001-g64a19591a293 #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:112 Allocated by task 2626: (stack is not available) Freed by task 2626: (stack is not available) The buggy address belongs to the object at ffffffe009e9a3c0 which belongs to the cache skbuff_head_cache of size 232 The buggy address is located 40 bytes inside of 232-byte region [ffffffe009e9a3c0, ffffffe009e9a4a8) The buggy address belongs to the page: page:ffffffcf02282680 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8a09a flags: 0xffe000000000200(slab|node=0|zone=0|lastcpupid=0x7ff) raw: 0ffe000000000200 0000000000000000 0000000400000001 ffffffe007de0500 raw: 0000000000000000 00000000000c000c 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY), pid 892, ts 738462711400, free_ts 735902748300 page_owner allocation stack trace missing page_owner free stack trace missing Memory state around the buggy address: ffffffe009e9a280: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffffffe009e9a300: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc >ffffffe009e9a380: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb ^ ffffffe009e9a400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffffffe009e9a480: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ==================================================================