loop0: detected capacity change from 0 to 1024
hfsplus: invalid length 2304 has been corrected to 255
==================================================================
BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x670/0x10f0 fs/hfsplus/unicode.c:186
Read of size 2 at addr ffff0000c1dbca18 by task syz-executor.0/4457

CPU: 1 PID: 4457 Comm: syz-executor.0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 print_address_description+0x78/0x30c mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:434 [inline]
 kasan_report+0xec/0x15c mm/kasan/report.c:451
 __asan_report_load2_noabort+0x44/0x50 mm/kasan/report_generic.c:307
 hfsplus_uni2asc+0x670/0x10f0 fs/hfsplus/unicode.c:186
 hfsplus_listxattr+0x4a8/0x9e8 fs/hfsplus/xattr.c:740
 vfs_listxattr fs/xattr.c:448 [inline]
 listxattr+0x29c/0x3e0 fs/xattr.c:783
 path_listxattr+0xdc/0x1b4 fs/xattr.c:807
 __do_sys_llistxattr fs/xattr.c:825 [inline]
 __se_sys_llistxattr fs/xattr.c:822 [inline]
 __arm64_sys_llistxattr+0x80/0x94 fs/xattr.c:822
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Allocated by task 4457:
 kasan_save_stack mm/kasan/common.c:38 [inline]
 kasan_set_track mm/kasan/common.c:46 [inline]
 set_alloc_info mm/kasan/common.c:434 [inline]
 ____kasan_kmalloc mm/kasan/common.c:513 [inline]
 __kasan_kmalloc+0xb0/0xf0 mm/kasan/common.c:522
 kasan_kmalloc include/linux/kasan.h:264 [inline]
 __kmalloc+0x298/0x44c mm/slub.c:4412
 kmalloc include/linux/slab.h:609 [inline]
 hfsplus_find_init+0x84/0x1bc fs/hfsplus/bfind.c:21
 hfsplus_listxattr+0x2fc/0x9e8 fs/hfsplus/xattr.c:700
 vfs_listxattr fs/xattr.c:448 [inline]
 listxattr+0x29c/0x3e0 fs/xattr.c:783
 path_listxattr+0xdc/0x1b4 fs/xattr.c:807
 __do_sys_llistxattr fs/xattr.c:825 [inline]
 __se_sys_llistxattr fs/xattr.c:822 [inline]
 __arm64_sys_llistxattr+0x80/0x94 fs/xattr.c:822
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the object at ffff0000c1dbc800
 which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 536 bytes inside of
 1024-byte region [ffff0000c1dbc800, ffff0000c1dbcc00)
The buggy address belongs to the page:
page:0000000059bece1a refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x101db8
head:0000000059bece1a order:3 compound_mapcount:0 compound_pincount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 0000000000000000 dead000000000122 ffff0000c0002780
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000c1dbc900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000c1dbc980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000c1dbca00: 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc
                            ^
 ffff0000c1dbca80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000c1dbcb00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================