[Android 6.1] KASAN: use-after-free Read in __ext4_check_dir_entry (2)
5 views
Skip to first unread message
syzbot
Apr 5, 2025, 9:22:29 AM4/5/25
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ca24c52e3c25 Revert "ANDROID: usb: Optimization the transf..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1545b404580000
kernel config: https://syzkaller.appspot.com/x/.config?x=82e71fa000d4b060
dashboard link: https://syzkaller.appspot.com/bug?extid=73836c72f168b93b604e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1345b404580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11635d98580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f658fff71131/disk-ca24c52e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c8e2204b751d/vmlinux-ca24c52e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f231bea1ecbd/bzImage-ca24c52e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/094fa5bb0818/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1152efb0580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+73836c...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
Read of size 2 at addr ffff888125221003 by task syz-executor388/304
CPU: 0 PID: 304 Comm: syz-executor388 Not tainted 6.1.129-syzkaller-00055-gca24c52e3c25 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:316 [inline]
print_report+0x158/0x4e0 mm/kasan/report.c:427
kasan_report+0x13c/0x170 mm/kasan/report.c:531
__asan_report_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:349
__ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
ext4_readdir+0x1290/0x3860 fs/ext4/dir.c:258
iterate_dir+0x265/0x600 fs/readdir.c:-1
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
__x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7d0d9dbe09
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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:00007ffdbc8182a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7d0d9dbe09
RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000000 R08: 00007ffdbc818300 R09: 00007ffdbc818300
R10: 00007ffdbc818300 R11: 0000000000000246 R12: 00007ffdbc818300
R13: 00007ffdbc8183e0 R14: 431bde82d7b634db R15: 00007f7d0da2401d
</TASK>
The buggy address belongs to the physical page:
page:ffffea0004948840 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x125221
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004948888 ffff8881f6e3c768 0000000000000000
raw: 0000000000000001 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 0x8140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO|__GFP_CMA), pid 304, tgid 304 (syz-executor388), ts 27857653527, free_ts 27860694717
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x213/0x220 mm/page_alloc.c:2637
prep_new_page+0x1b/0x110 mm/page_alloc.c:2644
get_page_from_freelist+0x3a98/0x3b10 mm/page_alloc.c:4539
__alloc_pages+0x234/0x610 mm/page_alloc.c:5837
__folio_alloc+0x15/0x40 mm/page_alloc.c:5869
__folio_alloc_node include/linux/gfp.h:245 [inline]
folio_alloc include/linux/gfp.h:274 [inline]
alloc_page_vma include/linux/gfp.h:283 [inline]
wp_page_copy+0x23b/0x1690 mm/memory.c:3202
do_wp_page+0xc5c/0xf30 mm/memory.c:-1
handle_pte_fault mm/memory.c:5175 [inline]
__handle_mm_fault mm/memory.c:5299 [inline]
handle_mm_fault+0x15e0/0x30e0 mm/memory.c:5439
do_user_addr_fault arch/x86/mm/fault.c:1323 [inline]
handle_page_fault arch/x86/mm/fault.c:1466 [inline]
exc_page_fault+0x3b3/0x6d0 arch/x86/mm/fault.c:1522
asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:608
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1545 [inline]
free_pcp_prepare mm/page_alloc.c:1619 [inline]
free_unref_page_prepare+0x9f1/0xa00 mm/page_alloc.c:3581
free_unref_page_list+0xf1/0x7b0 mm/page_alloc.c:3729
release_pages+0xef9/0xf50 mm/swap.c:1043
free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:315
tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:254 [inline]
tlb_flush_mmu mm/mmu_gather.c:261 [inline]
tlb_finish_mmu+0x1e0/0x3f0 mm/mmu_gather.c:361
unmap_region+0x2c1/0x310 mm/mmap.c:2402
do_mas_align_munmap+0xd27/0x13a0 mm/mmap.c:2668
do_mas_munmap+0x23e/0x2b0 mm/mmap.c:2726
__vm_munmap+0x263/0x3a0 mm/mmap.c:3025
__do_sys_munmap mm/mmap.c:3051 [inline]
__se_sys_munmap mm/mmap.c:3047 [inline]
__x64_sys_munmap+0x6b/0x80 mm/mmap.c:3047
x64_sys_call+0x75/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:12
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffff888125220f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888125220f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888125221000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888125221080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888125221100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_readdir:260: inode #2: block 255: comm syz-executor388: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0
---
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 syzk...@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
syzbot found the following issue on:
HEAD commit: ca24c52e3c25 Revert "ANDROID: usb: Optimization the transf..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1545b404580000
kernel config: https://syzkaller.appspot.com/x/.config?x=82e71fa000d4b060
dashboard link: https://syzkaller.appspot.com/bug?extid=73836c72f168b93b604e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1345b404580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11635d98580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f658fff71131/disk-ca24c52e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c8e2204b751d/vmlinux-ca24c52e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f231bea1ecbd/bzImage-ca24c52e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/094fa5bb0818/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1152efb0580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+73836c...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
Read of size 2 at addr ffff888125221003 by task syz-executor388/304
CPU: 0 PID: 304 Comm: syz-executor388 Not tainted 6.1.129-syzkaller-00055-gca24c52e3c25 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:316 [inline]
print_report+0x158/0x4e0 mm/kasan/report.c:427
kasan_report+0x13c/0x170 mm/kasan/report.c:531
__asan_report_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:349
__ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
ext4_readdir+0x1290/0x3860 fs/ext4/dir.c:258
iterate_dir+0x265/0x600 fs/readdir.c:-1
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
__x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7d0d9dbe09
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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:00007ffdbc8182a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7d0d9dbe09
RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000000 R08: 00007ffdbc818300 R09: 00007ffdbc818300
R10: 00007ffdbc818300 R11: 0000000000000246 R12: 00007ffdbc818300
R13: 00007ffdbc8183e0 R14: 431bde82d7b634db R15: 00007f7d0da2401d
</TASK>
The buggy address belongs to the physical page:
page:ffffea0004948840 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x125221
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004948888 ffff8881f6e3c768 0000000000000000
raw: 0000000000000001 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 0x8140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO|__GFP_CMA), pid 304, tgid 304 (syz-executor388), ts 27857653527, free_ts 27860694717
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x213/0x220 mm/page_alloc.c:2637
prep_new_page+0x1b/0x110 mm/page_alloc.c:2644
get_page_from_freelist+0x3a98/0x3b10 mm/page_alloc.c:4539
__alloc_pages+0x234/0x610 mm/page_alloc.c:5837
__folio_alloc+0x15/0x40 mm/page_alloc.c:5869
__folio_alloc_node include/linux/gfp.h:245 [inline]
folio_alloc include/linux/gfp.h:274 [inline]
alloc_page_vma include/linux/gfp.h:283 [inline]
wp_page_copy+0x23b/0x1690 mm/memory.c:3202
do_wp_page+0xc5c/0xf30 mm/memory.c:-1
handle_pte_fault mm/memory.c:5175 [inline]
__handle_mm_fault mm/memory.c:5299 [inline]
handle_mm_fault+0x15e0/0x30e0 mm/memory.c:5439
do_user_addr_fault arch/x86/mm/fault.c:1323 [inline]
handle_page_fault arch/x86/mm/fault.c:1466 [inline]
exc_page_fault+0x3b3/0x6d0 arch/x86/mm/fault.c:1522
asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:608
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1545 [inline]
free_pcp_prepare mm/page_alloc.c:1619 [inline]
free_unref_page_prepare+0x9f1/0xa00 mm/page_alloc.c:3581
free_unref_page_list+0xf1/0x7b0 mm/page_alloc.c:3729
release_pages+0xef9/0xf50 mm/swap.c:1043
free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:315
tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:254 [inline]
tlb_flush_mmu mm/mmu_gather.c:261 [inline]
tlb_finish_mmu+0x1e0/0x3f0 mm/mmu_gather.c:361
unmap_region+0x2c1/0x310 mm/mmap.c:2402
do_mas_align_munmap+0xd27/0x13a0 mm/mmap.c:2668
do_mas_munmap+0x23e/0x2b0 mm/mmap.c:2726
__vm_munmap+0x263/0x3a0 mm/mmap.c:3025
__do_sys_munmap mm/mmap.c:3051 [inline]
__se_sys_munmap mm/mmap.c:3047 [inline]
__x64_sys_munmap+0x6b/0x80 mm/mmap.c:3047
x64_sys_call+0x75/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:12
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffff888125220f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888125220f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888125221000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888125221080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888125221100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_readdir:260: inode #2: block 255: comm syz-executor388: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0
---
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 syzk...@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
syzbot
Apr 9, 2025, 11:24:38 AM4/9/25
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 760764029c6d Merge cf30300a216a ("usb: xhci: Fix NULL poin..
syzbot found the following issue on:
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17001d78580000
kernel config: https://syzkaller.appspot.com/x/.config?x=13938fba08c28a13
dashboard link: https://syzkaller.appspot.com/bug?extid=89297222eb000a6d3be5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177c8398580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1051b23f980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e942f533e5cc/disk-76076402.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2e1cb91597a/vmlinux-76076402.xz
kernel image: https://storage.googleapis.com/syzbot-assets/104ede48d7ac/bzImage-76076402.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b78c5c9fd32b/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1215d7e4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
CPU: 1 PID: 297 Comm: syz-executor867 Not tainted 5.15.178-syzkaller-00260-g760764029c6d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1c0 lib/dump_stack.c:106
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
print_address_description+0x87/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:427 [inline]
kasan_report+0x179/0x1c0 mm/kasan/report.c:444
__asan_report_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:307
__ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
ext4_readdir+0x14ba/0x3960 fs/ext4/dir.c:258
iterate_dir+0x265/0x600 fs/readdir.c:-1
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
__x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
__x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fc89810cf69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 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:00007ffe46b492a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fc89810cf69
RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 431bde82d7b634db R15: 00007ffe46b49310
</TASK>
The buggy address belongs to the page:
page:ffffea000494a140 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x125285
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004937b48 ffff8881f713c580 0000000000000000
raw: 0000000000000001 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 0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), pid 281, ts 18542887086, free_ts 18558686605
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1a3/0x1b0 mm/page_alloc.c:2605
prep_new_page+0x1b/0x110 mm/page_alloc.c:2611
get_page_from_freelist+0x3550/0x35d0 mm/page_alloc.c:4485
__alloc_pages+0x27e/0x8f0 mm/page_alloc.c:5780
__alloc_pages_node include/linux/gfp.h:591 [inline]
alloc_pages_node include/linux/gfp.h:605 [inline]
alloc_pages include/linux/gfp.h:618 [inline]
do_anonymous_page mm/memory.c:4066 [inline]
handle_pte_fault+0xec8/0x28f0 mm/memory.c:4906
__handle_mm_fault mm/memory.c:-1 [inline]
do_handle_mm_fault+0x20bc/0x2400 mm/memory.c:5330
handle_mm_fault include/linux/mm.h:1836 [inline]
do_user_addr_fault arch/x86/mm/fault.c:1418 [inline]
handle_page_fault arch/x86/mm/fault.c:1509 [inline]
exc_page_fault+0x3b5/0x7f0 arch/x86/mm/fault.c:1565
asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:606
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1472 [inline]
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pcp_prepare mm/page_alloc.c:1544 [inline]
free_unref_page_prepare+0x7c8/0x7d0 mm/page_alloc.c:3534
free_unref_page_list+0x14b/0xa60 mm/page_alloc.c:3671
release_pages+0x1310/0x1370 mm/swap.c:1009
free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:320
tlb_batch_pages_flush mm/mmu_gather.c:49 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:240 [inline]
tlb_flush_mmu mm/mmu_gather.c:247 [inline]
tlb_finish_mmu+0x177/0x320 mm/mmu_gather.c:338
unmap_region+0x304/0x350 mm/mmap.c:2680
__do_munmap+0x13e4/0x19d0 mm/mmap.c:2913
__do_sys_brk mm/mmap.c:257 [inline]
__se_sys_brk+0x403/0x860 mm/mmap.c:196
__x64_sys_brk+0x38/0x40 mm/mmap.c:196
x64_sys_call+0x7c/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:13
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Memory state around the buggy address:
ffff888125284f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888125285000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888125285080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888125285100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_readdir:260: inode #2: block 255: comm syz-executor867: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0
Reply all
Reply to author
Forward
0 new messages