==================================================================
BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x670/0x10f0 fs/hfsplus/unicode.c:186
Read of size 2 at addr ffff0000f64bca18 by task syz.3.4/4432

CPU: 1 PID: 4432 Comm: syz.3.4 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 print_address_description+0x88/0x218 mm/kasan/report.c:316
 print_report+0x50/0x68 mm/kasan/report.c:420
 kasan_report+0xa8/0x100 mm/kasan/report.c:524
 __asan_report_load2_noabort+0x2c/0x38 mm/kasan/report_generic.c:349
 hfsplus_uni2asc+0x670/0x10f0 fs/hfsplus/unicode.c:186
 hfsplus_listxattr+0x4a8/0x9e8 fs/hfsplus/xattr.c:740
 vfs_listxattr fs/xattr.c:457 [inline]
 listxattr+0x29c/0x3cc fs/xattr.c:804
 path_listxattr+0xdc/0x1b4 fs/xattr.c:828
 __do_sys_llistxattr fs/xattr.c:846 [inline]
 __se_sys_llistxattr fs/xattr.c:843 [inline]
 __arm64_sys_llistxattr+0x80/0x94 fs/xattr.c:843
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x138 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 4432:
 kasan_save_stack mm/kasan/common.c:45 [inline]
 kasan_set_track+0x4c/0x80 mm/kasan/common.c:52
 kasan_save_alloc_info+0x28/0x34 mm/kasan/generic.c:505
 ____kasan_kmalloc mm/kasan/common.c:374 [inline]
 __kasan_kmalloc+0xa0/0xb8 mm/kasan/common.c:383
 kasan_kmalloc include/linux/kasan.h:211 [inline]
 __do_kmalloc_node mm/slab_common.c:936 [inline]
 __kmalloc+0xec/0x178 mm/slab_common.c:949
 kmalloc include/linux/slab.h:568 [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:457 [inline]
 listxattr+0x29c/0x3cc fs/xattr.c:804
 path_listxattr+0xdc/0x1b4 fs/xattr.c:828
 __do_sys_llistxattr fs/xattr.c:846 [inline]
 __se_sys_llistxattr fs/xattr.c:843 [inline]
 __arm64_sys_llistxattr+0x80/0x94 fs/xattr.c:843
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x138 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 ffff0000f64bc800
 which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 536 bytes inside of
 1024-byte region [ffff0000f64bc800, ffff0000f64bcc00)

The buggy address belongs to the physical page:
page:000000009b2b845e refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1364b8
head:000000009b2b845e 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:
 ffff0000f64bc900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000f64bc980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000f64bca00: 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc
                            ^
 ffff0000f64bca80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000f64bcb00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================