UDF-fs: error (device loop5): udf_read_tagged: tag checksum failed, block 99: 0x27 != 0x4d UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) ================================================================== BUG: KASAN: slab-out-of-bounds in udf_write_aext+0x780/0x860 fs/udf/inode.c:2065 Write of size 4 at addr ffff88809745a530 by task syz-executor.5/13380 CPU: 0 PID: 13380 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354 kasan_report mm/kasan/report.c:412 [inline] __asan_report_store_n_noabort+0x8b/0xa0 mm/kasan/report.c:449 udf_write_aext+0x780/0x860 fs/udf/inode.c:2065 udf_add_entry+0xdab/0x2a20 fs/udf/namei.c:496 udf_mkdir+0x145/0x650 fs/udf/namei.c:693 vfs_mkdir+0x508/0x7a0 fs/namei.c:3819 do_mkdirat+0x262/0x2d0 fs/namei.c:3842 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f82a9cec0f9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f82a825e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f82a9e0bf80 RCX: 00007f82a9cec0f9 RDX: 0000000000000000 RSI: 00000000200000c0 RDI: ffffffffffffff9c RBP: 00007f82a9d47ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffa323134f R14: 00007f82a825e300 R15: 0000000000022000 Allocated by task 3544: kmem_cache_alloc_trace+0x12f/0x380 mm/slab.c:3625 kmalloc include/linux/slab.h:515 [inline] kzalloc include/linux/slab.h:709 [inline] ipv6_add_addr+0x489/0x1ca0 net/ipv6/addrconf.c:1030 addrconf_add_linklocal+0x1d6/0x410 net/ipv6/addrconf.c:3138 addrconf_addr_gen+0x39b/0x3e0 net/ipv6/addrconf.c:3269 addrconf_dev_config+0x275/0x410 net/ipv6/addrconf.c:3316 addrconf_notify+0x371/0x21f0 net/ipv6/addrconf.c:3551 notifier_call_chain+0xc0/0x230 kernel/notifier.c:93 netdev_state_change net/core/dev.c:1349 [inline] netdev_state_change+0x100/0x130 net/core/dev.c:1342 linkwatch_do_dev+0xaa/0x110 net/core/link_watch.c:164 __linkwatch_run_queue+0x22d/0x5d0 net/core/link_watch.c:202 linkwatch_event+0x4a/0x60 net/core/link_watch.c:237 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 Freed by task 8088: __cache_free mm/slab.c:3503 [inline] kfree+0xcc/0x210 mm/slab.c:3822 skb_free_head net/core/skbuff.c:563 [inline] skb_release_data+0x6de/0x920 net/core/skbuff.c:583 skb_release_all net/core/skbuff.c:640 [inline] __kfree_skb+0x46/0x60 net/core/skbuff.c:654 sk_eat_skb include/net/sock.h:2430 [inline] tcp_recvmsg+0x157c/0x2a90 net/ipv4/tcp.c:2161 inet_recvmsg+0x124/0x5c0 net/ipv4/af_inet.c:830 sock_recvmsg_nosec net/socket.c:859 [inline] sock_recvmsg net/socket.c:866 [inline] sock_recvmsg net/socket.c:862 [inline] sock_read_iter+0x339/0x470 net/socket.c:944 call_read_iter include/linux/fs.h:1815 [inline] new_sync_read fs/read_write.c:406 [inline] __vfs_read+0x518/0x750 fs/read_write.c:418 vfs_read+0x194/0x3c0 fs/read_write.c:452 ksys_read+0x12b/0x2a0 fs/read_write.c:579 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe The buggy address belongs to the object at ffff88809745a2c0 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 112 bytes to the right of 512-byte region [ffff88809745a2c0, ffff88809745a4c0) The buggy address belongs to the page: page:ffffea00025d1680 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffffea00026e2d88 ffffea00025fcd48 ffff88813bff0940 raw: 0000000000000000 ffff88809745a040 0000000100000006 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88809745a400: 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc ffff88809745a480: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88809745a500: fc fc fc fc fc fc fc fc 00 00 00 00 00 00 00 00 ^ ffff88809745a580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88809745a600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================