loop3: detected capacity change from 0 to 1024
==================================================================
BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x624/0x1018 fs/hfsplus/unicode.c:179
Read of size 2 at addr ffff0000ddd83a18 by task syz.3.63/4592

CPU: 0 PID: 4592 Comm: syz.3.63 Not tainted 6.1.115-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:284 [inline]
 print_report+0x174/0x4c0 mm/kasan/report.c:395
 kasan_report+0xd4/0x130 mm/kasan/report.c:495
 __asan_report_load2_noabort+0x2c/0x38 mm/kasan/report_generic.c:349
 hfsplus_uni2asc+0x624/0x1018 fs/hfsplus/unicode.c:179
 hfsplus_listxattr+0x5bc/0xc9c fs/hfsplus/xattr.c:736
 vfs_listxattr fs/xattr.c:457 [inline]
 listxattr+0x29c/0x3cc fs/xattr.c:804
 path_listxattr fs/xattr.c:828 [inline]
 __do_sys_llistxattr fs/xattr.c:846 [inline]
 __se_sys_llistxattr fs/xattr.c:843 [inline]
 __arm64_sys_llistxattr+0x13c/0x21c fs/xattr.c:843
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Allocated by task 4592:
 kasan_save_stack mm/kasan/common.c:45 [inline]
 kasan_set_track+0x4c/0x80 mm/kasan/common.c:52
 kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505
 ____kasan_kmalloc mm/kasan/common.c:374 [inline]
 __kasan_kmalloc+0xac/0xc4 mm/kasan/common.c:383
 kasan_kmalloc include/linux/kasan.h:211 [inline]
 __do_kmalloc_node mm/slab_common.c:936 [inline]
 __kmalloc+0xd8/0x1c4 mm/slab_common.c:949
 kmalloc include/linux/slab.h:562 [inline]
 hfsplus_find_init+0x84/0x1bc fs/hfsplus/bfind.c:21
 hfsplus_listxattr+0x31c/0xc9c fs/hfsplus/xattr.c:696
 vfs_listxattr fs/xattr.c:457 [inline]
 listxattr+0x29c/0x3cc fs/xattr.c:804
 path_listxattr fs/xattr.c:828 [inline]
 __do_sys_llistxattr fs/xattr.c:846 [inline]
 __se_sys_llistxattr fs/xattr.c:843 [inline]
 __arm64_sys_llistxattr+0x13c/0x21c fs/xattr.c:843
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

The buggy address belongs to the object at ffff0000ddd83800
 which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 536 bytes inside of
 1024-byte region [ffff0000ddd83800, ffff0000ddd83c00)

The buggy address belongs to the physical page:
page:00000000a838b306 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff0000ddd86800 pfn:0x11dd80
head:00000000a838b306 order:3 compound_mapcount:0 compound_pincount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 fffffc0003671800 dead000000000003 ffff0000c0002780
raw: ffff0000ddd86800 000000008010000d 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000ddd83900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000ddd83980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000ddd83a00: 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc
                            ^
 ffff0000ddd83a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000ddd83b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================