[syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    b71e635feefc Merge tag 'cgroup-for-6.19-rc5-fixes' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10efa99a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10cd15fa580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=152a4052580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/40abbbbc34a8/disk-b71e635f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/74edfb8073f7/vmlinux-b71e635f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3b5198043bfa/bzImage-b71e635f.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/7f1692afbc9c/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1609599a580000)
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/d09b0f5dc58e/mount_2.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8debf4b3f7c7391cd8eb@syzkaller.appspotmail.com

hpfs: filesystem error: invalid number of hotfixes: 2066844986, used: 2066844985; already mounted read-only
hpfs: filesystem error: improperly stopped
hpfs: filesystem error: warning: spare dnodes used, try chkdsk
hpfs: You really don't want any checks? You are crazy...
hpfs: hpfs_map_sector(): read error
hpfs: code page support is disabled
hpfs: filesystem error: map_dirent: not a directory
hpfs: hpfs_map_4sectors(): unaligned read
hpfs: filesystem error: unable to find root dir
==================================================================
BUG: KASAN: use-after-free in hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
Read of size 4 at addr ffff888052abe004 by task syz.0.27/6198

CPU: 1 UID: 0 PID: 6198 Comm: syz.0.27 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0xca/0x240 mm/kasan/report.c:482
 kasan_report+0x118/0x150 mm/kasan/report.c:595
 hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
 hpfs_bmap+0x22a/0x4d0 fs/hpfs/file.c:54
 hpfs_get_block+0xa8/0x6e0 fs/hpfs/file.c:87
 do_mpage_readpage+0x822/0x1990 fs/mpage.c:222
 mpage_readahead+0x3b0/0x790 fs/mpage.c:371
 read_pages+0x17a/0x580 mm/readahead.c:163
 page_cache_ra_unbounded+0x68b/0x8c0 mm/readahead.c:302
 filemap_get_pages+0x446/0x1ee0 mm/filemap.c:2690
 filemap_read+0x3f9/0x11a0 mm/filemap.c:2800
 __kernel_read+0x4d8/0x970 fs/read_write.c:530
 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline]
 ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline]
 ima_calc_file_hash+0x86a/0x1700 security/integrity/ima/ima_crypto.c:568
 ima_collect_measurement+0x42e/0x900 security/integrity/ima/ima_api.c:293
 process_measurement+0x112a/0x1a80 security/integrity/ima/ima_main.c:406
 ima_file_check+0xd9/0x130 security/integrity/ima/ima_main.c:663
 security_file_post_open+0xbb/0x290 security/security.c:2652
 do_open fs/namei.c:4639 [inline]
 path_openat+0x3472/0x3df0 fs/namei.c:4796
 do_filp_open+0x1fa/0x410 fs/namei.c:4823
 do_sys_openat2+0x121/0x200 fs/open.c:1430
 do_sys_open fs/open.c:1436 [inline]
 __do_sys_openat fs/open.c:1452 [inline]
 __se_sys_openat fs/open.c:1447 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1447
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb59539f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3ac53cb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fb5955f5fa0 RCX: 00007fb59539f749
RDX: 0000000000000000 RSI: 0000200000004280 RDI: ffffffffffffff9c
RBP: 00007fb595423f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb5955f5fa0 R14: 00007fb5955f5fa0 R15: 0000000000000004
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x7fb58c615 pfn:0x52abe
flags: 0x80000000000000(node=0|zone=1)
raw: 0080000000000000 ffffea00014aafc8 ffff8880b8842d30 0000000000000000
raw: 00000007fb58c615 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|__GFP_COMP), pid 6198, tgid 6198 (syz.0.27), ts 130045840131, free_ts 130049000115
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x234/0x290 mm/page_alloc.c:1857
 prep_new_page mm/page_alloc.c:1865 [inline]
 get_page_from_freelist+0x28c0/0x2960 mm/page_alloc.c:3915
 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5210
 alloc_pages_mpol+0xd1/0x380 mm/mempolicy.c:2486
 folio_alloc_mpol_noprof mm/mempolicy.c:2505 [inline]
 vma_alloc_folio_noprof+0xe4/0x280 mm/mempolicy.c:2540
 folio_prealloc+0x30/0x180 mm/memory.c:-1
 alloc_anon_folio mm/memory.c:5165 [inline]
 do_anonymous_page mm/memory.c:5222 [inline]
 do_pte_missing+0x86a/0x27a0 mm/memory.c:4399
 handle_pte_fault mm/memory.c:6273 [inline]
 __handle_mm_fault mm/memory.c:6411 [inline]
 handle_mm_fault+0xcc1/0x1330 mm/memory.c:6580
 do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336
 handle_page_fault arch/x86/mm/fault.c:1476 [inline]
 exc_page_fault+0x71/0xd0 arch/x86/mm/fault.c:1532
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
page last free pid 6198 tgid 6198 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1406 [inline]
 free_unref_folios+0xc28/0x1810 mm/page_alloc.c:3000
 folios_put_refs+0x569/0x670 mm/swap.c:1002
 free_pages_and_swap_cache+0x4be/0x520 mm/swap_state.c:358
 __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline]
 tlb_batch_pages_flush mm/mmu_gather.c:149 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:397 [inline]
 tlb_flush_mmu+0x3a0/0x680 mm/mmu_gather.c:404
 tlb_finish_mmu+0xc3/0x1d0 mm/mmu_gather.c:497
 vms_clear_ptes+0x42b/0x530 mm/vma.c:1238
 vms_complete_munmap_vmas+0x206/0x8a0 mm/vma.c:1280
 do_vmi_align_munmap+0x372/0x450 mm/vma.c:1539
 do_vmi_munmap+0x253/0x2e0 mm/vma.c:1587
 __vm_munmap+0x207/0x380 mm/vma.c:3203
 __do_sys_munmap mm/mmap.c:1077 [inline]
 __se_sys_munmap mm/mmap.c:1074 [inline]
 __x64_sys_munmap+0x60/0x70 mm/mmap.c:1074
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff888052abdf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888052abdf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888052abe000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff888052abe080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888052abe100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot]

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/hpfs/anode.c
patch: **** missing line number at line 4: @@ -XX,6 +XX,16 @@ secno hpfs_bplus_lookup(struct super_block *s, struct inode *inode,




Tested on:

commit:         39d33893 Merge tag 'drm-fixes-2026-01-16' of https://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15ee23fa580000

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot]

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: use-after-free Read in hpfs_bplus_lookup

hpfs: filesystem error: warning: spare dnodes used, try chkdsk
hpfs: You really don't want any checks? You are crazy...
hpfs: hpfs_map_sector(): read error
hpfs: code page support is disabled
hpfs: filesystem error: map_dirent: not a directory
hpfs: hpfs_map_4sectors(): unaligned read
hpfs: filesystem error: unable to find root dir
==================================================================
BUG: KASAN: use-after-free in hpfs_bplus_lookup+0x58c/0x9b0 fs/hpfs/anode.c:50
Read of size 4 at addr ffff8880521e8004 by task syz.0.17/6571

CPU: 1 UID: 0 PID: 6571 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0xba/0x230 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 hpfs_bplus_lookup+0x58c/0x9b0 fs/hpfs/anode.c:50
 hpfs_bmap+0x230/0x4e0 fs/hpfs/file.c:54
 hpfs_get_block+0xa8/0x6e0 fs/hpfs/file.c:87
 do_mpage_readpage+0x801/0x1980 fs/mpage.c:222
 mpage_readahead+0x407/0x830 fs/mpage.c:371
 read_pages+0x193/0x5a0 mm/readahead.c:163
 page_cache_ra_unbounded+0x68a/0x8c0 mm/readahead.c:302
 filemap_get_pages+0x47c/0x1e60 mm/filemap.c:2690
 filemap_read+0x44a/0x1240 mm/filemap.c:2800
 __kernel_read+0x50d/0x9c0 fs/read_write.c:530
 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline]
 ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline]
 ima_calc_file_hash+0x12cf/0x1800 security/integrity/ima/ima_crypto.c:568
 ima_collect_measurement+0x491/0x930 security/integrity/ima/ima_api.c:293
 process_measurement+0x12ec/0x1cc0 security/integrity/ima/ima_main.c:406
 ima_file_check+0xdf/0x130 security/integrity/ima/ima_main.c:663
 security_file_post_open+0xb3/0x260 security/security.c:2652
 do_open fs/namei.c:4639 [inline]
 path_openat+0x350e/0x3e70 fs/namei.c:4796
 do_filp_open+0x22d/0x490 fs/namei.c:4823
 do_sys_openat2+0x12f/0x220 fs/open.c:1430
 do_sys_open fs/open.c:1436 [inline]
 __do_sys_openat fs/open.c:1452 [inline]
 __se_sys_openat fs/open.c:1447 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1447
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fad6901aef9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fad6867e028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fad69285fa0 RCX: 00007fad6901aef9
RDX: 0000000000000000 RSI: 0000200000004280 RDI: ffffffffffffff9c
RBP: 00007fad690afee0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fad69286038 R14: 00007fad69285fa0 R15: 00007ffc492fd528
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x24d pfn:0x521e8
flags: 0x80000000000000(node=0|zone=1)
raw: 0080000000000000 ffffea0001487748 ffffea0001487a48 0000000000000000
raw: 000000000000024d 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), pid 6571, tgid 6570 (syz.0.17), ts 163321665268, free_ts 163796733751
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x228/0x280 mm/page_alloc.c:1884
 prep_new_page mm/page_alloc.c:1892 [inline]
 get_page_from_freelist+0x28bb/0x2950 mm/page_alloc.c:3945
 __alloc_frozen_pages_noprof+0x18d/0x380 mm/page_alloc.c:5240
 alloc_pages_mpol+0xd1/0x380 mm/mempolicy.c:2486
 folio_alloc_mpol_noprof+0x39/0xe0 mm/mempolicy.c:2505
 shmem_alloc_folio mm/shmem.c:1890 [inline]
 shmem_alloc_and_add_folio mm/shmem.c:1932 [inline]
 shmem_get_folio_gfp+0x644/0x1a80 mm/shmem.c:2556
 shmem_get_folio mm/shmem.c:2662 [inline]
 shmem_write_begin+0x166/0x320 mm/shmem.c:3315
 generic_perform_write+0x2af/0x8b0 mm/filemap.c:4314
 shmem_file_write_iter+0xfb/0x120 mm/shmem.c:3490
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x629/0xba0 fs/read_write.c:686
 ksys_write+0x156/0x270 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 6498 tgid 6498 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1433 [inline]
 free_unref_folios+0xc13/0x17f0 mm/page_alloc.c:3030
 folios_put_refs+0x56f/0x680 mm/swap.c:1002
 folio_batch_release include/linux/pagevec.h:101 [inline]
 shmem_undo_range+0x529/0x1570 mm/shmem.c:1137
 shmem_truncate_range mm/shmem.c:1249 [inline]
 shmem_evict_inode+0x240/0x9e0 mm/shmem.c:1379
 evict+0x61e/0xb10 fs/inode.c:837
 __dentry_kill+0x209/0x660 fs/dcache.c:670
 finish_dput+0xc9/0x480 fs/dcache.c:879
 __fput+0x6a0/0xa80 fs/file_table.c:476
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]
 exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:75
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]
 do_syscall_64+0x2b7/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff8880521e7f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880521e7f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880521e8000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff8880521e8080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8880521e8100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


Tested on:

commit:         39d33893 Merge tag 'drm-fixes-2026-01-16' of https://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=138c939a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c33bf4a3a0c7a4f1
dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1371239a580000

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot]

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: use-after-free Read in hpfs_bplus_lookup

=== CRASH WILL HAPPEN ON NEXT LINE IF UAF ===
=== external[120]: about to access ffff8880545bffe0 ===
=== CRASH WILL HAPPEN ON NEXT LINE IF UAF ===
=== external[121]: about to access ffff8880545bffec ===
=== CRASH WILL HAPPEN ON NEXT LINE IF UAF ===
=== external[122]: about to access ffff8880545bfff8 ===
=== CRASH WILL HAPPEN ON NEXT LINE IF UAF ===
=== external[123]: about to access ffff8880545c0004 ===
=== CRASH WILL HAPPEN ON NEXT LINE IF UAF ===
==================================================================
BUG: KASAN: use-after-free in hpfs_bplus_lookup+0x7d5/0xbd0 fs/hpfs/anode.c:68
Read of size 4 at addr ffff8880545c0004 by task syz.0.21/6731

CPU: 1 UID: 0 PID: 6731 Comm: syz.0.21 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0xba/0x230 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 hpfs_bplus_lookup+0x7d5/0xbd0 fs/hpfs/anode.c:68
 hpfs_bmap+0x230/0x4e0 fs/hpfs/file.c:54
 hpfs_get_block+0xa8/0x6e0 fs/hpfs/file.c:87
 do_mpage_readpage+0x801/0x1980 fs/mpage.c:222
 mpage_readahead+0x407/0x830 fs/mpage.c:371
 read_pages+0x193/0x5a0 mm/readahead.c:163
 page_cache_ra_unbounded+0x68a/0x8c0 mm/readahead.c:302
 filemap_get_pages+0x47c/0x1e60 mm/filemap.c:2690
 filemap_read+0x44a/0x1240 mm/filemap.c:2800
 __kernel_read+0x50d/0x9c0 fs/read_write.c:530
 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline]
 ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline]
 ima_calc_file_hash+0x12cf/0x1800 security/integrity/ima/ima_crypto.c:568
 ima_collect_measurement+0x491/0x930 security/integrity/ima/ima_api.c:293
 process_measurement+0x12ec/0x1cc0 security/integrity/ima/ima_main.c:406
 ima_file_check+0xdf/0x130 security/integrity/ima/ima_main.c:663
 security_file_post_open+0xb3/0x260 security/security.c:2652
 do_open fs/namei.c:4639 [inline]
 path_openat+0x350e/0x3e70 fs/namei.c:4796
 do_filp_open+0x22d/0x490 fs/namei.c:4823
 do_sys_openat2+0x12f/0x220 fs/open.c:1430
 do_sys_open fs/open.c:1436 [inline]
 __do_sys_openat fs/open.c:1452 [inline]
 __se_sys_openat fs/open.c:1447 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1447
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7feb1639aef9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007feb159fe028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007feb16605fa0 RCX: 00007feb1639aef9
RDX: 0000000000000000 RSI: 0000200000004280 RDI: ffffffffffffff9c
RBP: 00007feb1642fee0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007feb16606038 R14: 00007feb16605fa0 R15: 00007fff6450b218
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xb10 pfn:0x545c0
flags: 0x80000000000000(node=0|zone=1)
page_type: f0(buddy)
raw: 0080000000000000 ffff88813fffc380 ffffea0001525008 0000000000000000
raw: 0000000000000b10 0000000000000006 00000000f0000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), pid 6731, tgid 6730 (syz.0.21), ts 168496747643, free_ts 169044969619
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x228/0x280 mm/page_alloc.c:1884
 prep_new_page mm/page_alloc.c:1892 [inline]
 get_page_from_freelist+0x28bb/0x2950 mm/page_alloc.c:3945
 __alloc_frozen_pages_noprof+0x18d/0x380 mm/page_alloc.c:5240
 alloc_pages_mpol+0xd1/0x380 mm/mempolicy.c:2486
 folio_alloc_mpol_noprof+0x39/0xe0 mm/mempolicy.c:2505
 shmem_alloc_folio mm/shmem.c:1890 [inline]
 shmem_alloc_and_add_folio mm/shmem.c:1932 [inline]
 shmem_get_folio_gfp+0x644/0x1a80 mm/shmem.c:2556
 shmem_get_folio mm/shmem.c:2662 [inline]
 shmem_write_begin+0x166/0x320 mm/shmem.c:3315
 generic_perform_write+0x2af/0x8b0 mm/filemap.c:4314
 shmem_file_write_iter+0xfb/0x120 mm/shmem.c:3490
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x629/0xba0 fs/read_write.c:686
 ksys_write+0x156/0x270 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 6731 tgid 6730 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1433 [inline]
 free_unref_folios+0xc13/0x17f0 mm/page_alloc.c:3030
 folios_put_refs+0x56f/0x680 mm/swap.c:1002
 folio_batch_release include/linux/pagevec.h:101 [inline]
 shmem_undo_range+0x529/0x1570 mm/shmem.c:1137
 shmem_truncate_range mm/shmem.c:1249 [inline]
 shmem_evict_inode+0x240/0x9e0 mm/shmem.c:1379
 evict+0x61e/0xb10 fs/inode.c:837
 __dentry_kill+0x209/0x660 fs/dcache.c:670
 finish_dput+0xc9/0x480 fs/dcache.c:879
 __fput+0x6a0/0xa80 fs/file_table.c:476
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]
 exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:75
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]
 do_syscall_64+0x2b7/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff8880545bff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880545bff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880545c0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff8880545c0080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8880545c0100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


Tested on:

commit:         39d33893 Merge tag 'drm-fixes-2026-01-16' of https://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13f523fa580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c33bf4a3a0c7a4f1
dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1365239a580000

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[syzbot]

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+8debf4b3f7c7391cd8eb@syzkaller.appspotmail.com
Tested-by: syzbot+8debf4b3f7c7391cd8eb@syzkaller.appspotmail.com

Tested on:

commit:         d3eeb99b Merge tag 'block-6.19-20260116' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109d239a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c33bf4a3a0c7a4f1
dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1142939a580000

Note: testing is done by a robot and is best-effort only.

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[Christoph Hellwig]

Any idea why this Ccs the xfs list?

On Fri, Jan 16, 2026 at 01:04:26PM -0800, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    b71e635feefc Merge tag 'cgroup-for-6.19-rc5-fixes' of git:..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10efa99a580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
> dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
> compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10cd15fa580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=152a4052580000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/40abbbbc34a8/disk-b71e635f.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/74edfb8073f7/vmlinux-b71e635f.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/3b5198043bfa/bzImage-b71e635f.xz
> mounted in repro #1: https://storage.googleapis.com/syzbot-assets/7f1692afbc9c/mount_0.gz
>   fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1609599a580000)
> mounted in repro #2: https://storage.googleapis.com/syzbot-assets/d09b0f5dc58e/mount_2.gz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8debf4b3f7c7391cd8eb@syzkaller.appspotmail.com
> 
> hpfs: filesystem error: invalid number of hotfixes: 2066844986, used: 2066844985; already mounted read-only
> hpfs: filesystem error: improperly stopped
> hpfs: filesystem error: warning: spare dnodes used, try chkdsk
> hpfs: You really don't want any checks? You are crazy...
> hpfs: hpfs_map_sector(): read error
> hpfs: code page support is disabled
> hpfs: filesystem error: map_dirent: not a directory
> hpfs: hpfs_map_4sectors(): unaligned read
> hpfs: filesystem error: unable to find root dir
> ==================================================================
> BUG: KASAN: use-after-free in hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
> Read of size 4 at addr ffff888052abe004 by task syz.0.27/6198
> 
> CPU: 1 UID: 0 PID: 6198 Comm: syz.0.27 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
> Call Trace:
>  <TASK>
>  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
>  print_address_description mm/kasan/report.c:378 [inline]
>  print_report+0xca/0x240 mm/kasan/report.c:482
>  kasan_report+0x118/0x150 mm/kasan/report.c:595
>  hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
>  hpfs_bmap+0x22a/0x4d0 fs/hpfs/file.c:54
>  hpfs_get_block+0xa8/0x6e0 fs/hpfs/file.c:87
>  do_mpage_readpage+0x822/0x1990 fs/mpage.c:222
>  mpage_readahead+0x3b0/0x790 fs/mpage.c:371
>  read_pages+0x17a/0x580 mm/readahead.c:163
>  page_cache_ra_unbounded+0x68b/0x8c0 mm/readahead.c:302
>  filemap_get_pages+0x446/0x1ee0 mm/filemap.c:2690
>  filemap_read+0x3f9/0x11a0 mm/filemap.c:2800
>  __kernel_read+0x4d8/0x970 fs/read_write.c:530
>  integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
>  ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline]
>  ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline]
>  ima_calc_file_hash+0x86a/0x1700 security/integrity/ima/ima_crypto.c:568
>  ima_collect_measurement+0x42e/0x900 security/integrity/ima/ima_api.c:293
>  process_measurement+0x112a/0x1a80 security/integrity/ima/ima_main.c:406
>  ima_file_check+0xd9/0x130 security/integrity/ima/ima_main.c:663
>  security_file_post_open+0xbb/0x290 security/security.c:2652
>  do_open fs/namei.c:4639 [inline]
>  path_openat+0x3472/0x3df0 fs/namei.c:4796
>  do_filp_open+0x1fa/0x410 fs/namei.c:4823
>  do_sys_openat2+0x121/0x200 fs/open.c:1430
>  do_sys_open fs/open.c:1436 [inline]
>  __do_sys_openat fs/open.c:1452 [inline]
>  __se_sys_openat fs/open.c:1447 [inline]
>  __x64_sys_openat+0x138/0x170 fs/open.c:1447
>  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>  do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fb59539f749
> Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fff3ac53cb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> RAX: ffffffffffffffda RBX: 00007fb5955f5fa0 RCX: 00007fb59539f749
> RDX: 0000000000000000 RSI: 0000200000004280 RDI: ffffffffffffff9c
> RBP: 00007fb595423f91 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007fb5955f5fa0 R14: 00007fb5955f5fa0 R15: 0000000000000004
>  </TASK>
> 
> The buggy address belongs to the physical page:
> page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x7fb58c615 pfn:0x52abe
> flags: 0x80000000000000(node=0|zone=1)
> raw: 0080000000000000 ffffea00014aafc8 ffff8880b8842d30 0000000000000000
> raw: 00000007fb58c615 0000000000000000 00000000ffffffff 0000000000000000
> page dumped because: kasan: bad access detected
> page_owner tracks the page as freed
> page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|__GFP_COMP), pid 6198, tgid 6198 (syz.0.27), ts 130045840131, free_ts 130049000115
>  set_page_owner include/linux/page_owner.h:32 [inline]
>  post_alloc_hook+0x234/0x290 mm/page_alloc.c:1857
>  prep_new_page mm/page_alloc.c:1865 [inline]
>  get_page_from_freelist+0x28c0/0x2960 mm/page_alloc.c:3915
>  __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5210
>  alloc_pages_mpol+0xd1/0x380 mm/mempolicy.c:2486
>  folio_alloc_mpol_noprof mm/mempolicy.c:2505 [inline]
>  vma_alloc_folio_noprof+0xe4/0x280 mm/mempolicy.c:2540
>  folio_prealloc+0x30/0x180 mm/memory.c:-1
>  alloc_anon_folio mm/memory.c:5165 [inline]
>  do_anonymous_page mm/memory.c:5222 [inline]
>  do_pte_missing+0x86a/0x27a0 mm/memory.c:4399
>  handle_pte_fault mm/memory.c:6273 [inline]
>  __handle_mm_fault mm/memory.c:6411 [inline]
>  handle_mm_fault+0xcc1/0x1330 mm/memory.c:6580
>  do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336
>  handle_page_fault arch/x86/mm/fault.c:1476 [inline]
>  exc_page_fault+0x71/0xd0 arch/x86/mm/fault.c:1532
>  asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
> page last free pid 6198 tgid 6198 stack trace:
>  reset_page_owner include/linux/page_owner.h:25 [inline]
>  free_pages_prepare mm/page_alloc.c:1406 [inline]
>  free_unref_folios+0xc28/0x1810 mm/page_alloc.c:3000
>  folios_put_refs+0x569/0x670 mm/swap.c:1002
>  free_pages_and_swap_cache+0x4be/0x520 mm/swap_state.c:358
>  __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline]
>  tlb_batch_pages_flush mm/mmu_gather.c:149 [inline]
>  tlb_flush_mmu_free mm/mmu_gather.c:397 [inline]
>  tlb_flush_mmu+0x3a0/0x680 mm/mmu_gather.c:404
>  tlb_finish_mmu+0xc3/0x1d0 mm/mmu_gather.c:497
>  vms_clear_ptes+0x42b/0x530 mm/vma.c:1238
>  vms_complete_munmap_vmas+0x206/0x8a0 mm/vma.c:1280
>  do_vmi_align_munmap+0x372/0x450 mm/vma.c:1539
>  do_vmi_munmap+0x253/0x2e0 mm/vma.c:1587
>  __vm_munmap+0x207/0x380 mm/vma.c:3203
>  __do_sys_munmap mm/mmap.c:1077 [inline]
>  __se_sys_munmap mm/mmap.c:1074 [inline]
>  __x64_sys_munmap+0x60/0x70 mm/mmap.c:1074
>  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>  do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> Memory state around the buggy address:
>  ffff888052abdf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>  ffff888052abdf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >ffff888052abe000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>                    ^
>  ffff888052abe080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  ffff888052abe100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ==================================================================
> 
> 
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
> 
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> 
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
> 
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
> 
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
> 
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
> 
> If you want to undo deduplication, reply with:
> #syz undup
> 
---end quoted text---

Re: [syzbot] [xfs?] KASAN: use-after-free Read in hpfs_bplus_lookup

[Aleksandr Nogikh]

On Mon, Jan 19, 2026 at 7:36 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> Any idea why this Ccs the xfs list?

Somehow, the reproducers first mount xfs and only then hpfs, so syzbot
also tagged the xfs list.

>
> On Fri, Jan 16, 2026 at 01:04:26PM -0800, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    b71e635feefc Merge tag 'cgroup-for-6.19-rc5-fixes' of git:..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10efa99a580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
> > dashboard link: https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
> > compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10cd15fa580000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=152a4052580000
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/40abbbbc34a8/disk-b71e635f.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/74edfb8073f7/vmlinux-b71e635f.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/3b5198043bfa/bzImage-b71e635f.xz
> > mounted in repro #1: https://storage.googleapis.com/syzbot-assets/7f1692afbc9c/mount_0.gz
> >   fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1609599a580000)
> > mounted in repro #2: https://storage.googleapis.com/syzbot-assets/d09b0f5dc58e/mount_2.gz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+8debf4b3f7c7391cd8eb@syzkaller.appspotmail.com
> >
> > hpfs: filesystem error: invalid number of hotfixes: 2066844986, used: 2066844985; already mounted read-only
> > hpfs: filesystem error: improperly stopped
> > hpfs: filesystem error: warning: spare dnodes used, try chkdsk
> > hpfs: You really don't want any checks? You are crazy...
> > hpfs: hpfs_map_sector(): read error
> > hpfs: code page support is disabled
> > hpfs: filesystem error: map_dirent: not a directory
> > hpfs: hpfs_map_4sectors(): unaligned read
> > hpfs: filesystem error: unable to find root dir
> > ==================================================================
> > BUG: KASAN: use-after-free in hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
> > Read of size 4 at addr ffff888052abe004 by task syz.0.27/6198
> >
> > CPU: 1 UID: 0 PID: 6198 Comm: syz.0.27 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
> > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
> > Call Trace:
> >  <TASK>
> >  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
> >  print_address_description mm/kasan/report.c:378 [inline]
> >  print_report+0xca/0x240 mm/kasan/report.c:482
> >  kasan_report+0x118/0x150 mm/kasan/report.c:595
> >  hpfs_bplus_lookup+0x4dc/0x860 fs/hpfs/anode.c:38
> >  hpfs_bmap+0x22a/0x4d0 fs/hpfs/file.c:54
> >  hpfs_get_block+0xa8/0x6e0 fs/hpfs/file.c:87
> >  do_mpage_readpage+0x822/0x1990 fs/mpage.c:222
> >  mpage_readahead+0x3b0/0x790 fs/mpage.c:371
> >  read_pages+0x17a/0x580 mm/readahead.c:163
> >  page_cache_ra_unbounded+0x68b/0x8c0 mm/readahead.c:302
> >  filemap_get_pages+0x446/0x1ee0 mm/filemap.c:2690
> >  filemap_read+0x3f9/0x11a0 mm/filemap.c:2800
> >  __kernel_read+0x4d8/0x970 fs/read_write.c:530
> >  integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
> >  ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:480 [inline]
> >  ima_calc_file_shash security/integrity/ima/ima_crypto.c:511 [inline]
> >  ima_calc_file_hash+0x86a/0x1700 security/integrity/ima/ima_crypto.c:568
> >  ima_collect_measurement+0x42e/0x900 security/integrity/ima/ima_api.c:293
> >  process_measurement+0x112a/0x1a80 security/integrity/ima/ima_main.c:406
> >  ima_file_check+0xd9/0x130 security/integrity/ima/ima_main.c:663
> >  security_file_post_open+0xbb/0x290 security/security.c:2652
> >  do_open fs/namei.c:4639 [inline]
> >  path_openat+0x3472/0x3df0 fs/namei.c:4796
> >  do_filp_open+0x1fa/0x410 fs/namei.c:4823
> >  do_sys_openat2+0x121/0x200 fs/open.c:1430
> >  do_sys_open fs/open.c:1436 [inline]
> >  __do_sys_openat fs/open.c:1452 [inline]
> >  __se_sys_openat fs/open.c:1447 [inline]
> >  __x64_sys_openat+0x138/0x170 fs/open.c:1447
> >  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> >  do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
> >  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> > RIP: 0033:0x7fb59539f749
> > Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
> > RSP: 002b:00007fff3ac53cb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> > RAX: ffffffffffffffda RBX: 00007fb5955f5fa0 RCX: 00007fb59539f749
> > RDX: 0000000000000000 RSI: 0000200000004280 RDI: ffffffffffffff9c
> > RBP: 00007fb595423f91 R08: 0000000000000000 R09: 0000000000000000
> > R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> > R13: 00007fb5955f5fa0 R14: 00007fb5955f5fa0 R15: 0000000000000004
> >  </TASK>
> >
> > The buggy address belongs to the physical page:
> > page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x7fb58c615 pfn:0x52abe
> > flags: 0x80000000000000(node=0|zone=1)
> > raw: 0080000000000000 ffffea00014aafc8 ffff8880b8842d30 0000000000000000
> > raw: 00000007fb58c615 0000000000000000 00000000ffffffff 0000000000000000
> > page dumped because: kasan: bad access detected
> > page_owner tracks the page as freed
> > page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|__GFP_COMP), pid 6198, tgid 6198 (syz.0.27), ts 130045840131, free_ts 130049000115
> >  set_page_owner include/linux/page_owner.h:32 [inline]
> >  post_alloc_hook+0x234/0x290 mm/page_alloc.c:1857
> >  prep_new_page mm/page_alloc.c:1865 [inline]
> >  get_page_from_freelist+0x28c0/0x2960 mm/page_alloc.c:3915
> >  __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5210
> >  alloc_pages_mpol+0xd1/0x380 mm/mempolicy.c:2486
> >  folio_alloc_mpol_noprof mm/mempolicy.c:2505 [inline]
> >  vma_alloc_folio_noprof+0xe4/0x280 mm/mempolicy.c:2540
> >  folio_prealloc+0x30/0x180 mm/memory.c:-1
> >  alloc_anon_folio mm/memory.c:5165 [inline]
> >  do_anonymous_page mm/memory.c:5222 [inline]
> >  do_pte_missing+0x86a/0x27a0 mm/memory.c:4399
> >  handle_pte_fault mm/memory.c:6273 [inline]
> >  __handle_mm_fault mm/memory.c:6411 [inline]
> >  handle_mm_fault+0xcc1/0x1330 mm/memory.c:6580
> >  do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336
> >  handle_page_fault arch/x86/mm/fault.c:1476 [inline]
> >  exc_page_fault+0x71/0xd0 arch/x86/mm/fault.c:1532
> >  asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
> > page last free pid 6198 tgid 6198 stack trace:
> >  reset_page_owner include/linux/page_owner.h:25 [inline]
> >  free_pages_prepare mm/page_alloc.c:1406 [inline]
> >  free_unref_folios+0xc28/0x1810 mm/page_alloc.c:3000
> >  folios_put_refs+0x569/0x670 mm/swap.c:1002
> >  free_pages_and_swap_cache+0x4be/0x520 mm/swap_state.c:358
> >  __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline]
> >  tlb_batch_pages_flush mm/mmu_gather.c:149 [inline]
> >  tlb_flush_mmu_free mm/mmu_gather.c:397 [inline]
> >  tlb_flush_mmu+0x3a0/0x680 mm/mmu_gather.c:404
> >  tlb_finish_mmu+0xc3/0x1d0 mm/mmu_gather.c:497
> >  vms_clear_ptes+0x42b/0x530 mm/vma.c:1238
> >  vms_complete_munmap_vmas+0x206/0x8a0 mm/vma.c:1280
> >  do_vmi_align_munmap+0x372/0x450 mm/vma.c:1539
> >  do_vmi_munmap+0x253/0x2e0 mm/vma.c:1587
> >  __vm_munmap+0x207/0x380 mm/vma.c:3203
> >  __do_sys_munmap mm/mmap.c:1077 [inline]
> >  __se_sys_munmap mm/mmap.c:1074 [inline]
> >  __x64_sys_munmap+0x60/0x70 mm/mmap.c:1074
> >  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> >  do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
> >  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> >
> > Memory state around the buggy address:
> >  ffff888052abdf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >  ffff888052abdf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >ffff888052abe000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >                    ^
> >  ffff888052abe080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >  ffff888052abe100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > ==================================================================
> >
> >
> > ---
> > This report is generated by a bot. It may contain errors.
> > See https://goo.gl/tpsmEJ for more information about syzbot.
> > syzbot engineers can be reached at syzkaller@googlegroups.com.
> >
> > syzbot will keep track of this issue. See:
> > https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> >
> > If the report is already addressed, let syzbot know by replying with:
> > #syz fix: exact-commit-title
> >
> > If you want syzbot to run the reproducer, reply with:
> > #syz test: git://repo/address.git branch-or-commit-hash
> > If you attach or paste a git patch, syzbot will apply it before testing.
> >
> > If you want to overwrite report's subsystems, reply with:
> > #syz set subsystems: new-subsystem
> > (See the list of subsystem names on the web dashboard)
> >
> > If the report is a duplicate of another one, reply with:
> > #syz dup: exact-subject-of-another-report
> >
> > If you want to undo deduplication, reply with:
> > #syz undup
> >
> ---end quoted text---
>