KASAN: use-after-free Read in ext4_xattr_list_entries (2)

Status: upstream: reported on 2026/06/09 21:03
Subsystems: ext4
Labels: actionable prio:high
[Documentation on labels]
Reported-by: syzbot+3fbf2337de43f5581aec@syzkaller.appspotmail.com
First crash: 64d, last: 1d20h
✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
3d7b2494 assessment-security DenialOfService: ✅ Exploitable: ✅ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ✅ KASAN: use-after-free Read in ext4_xattr_list_entries (2) 2026/06/09 20:18 2026/06/09 20:18 2026/06/09 21:13 c36c07f6
b34af3c3 moderation Actionable: ✅ KASAN: use-after-free Read in ext4_xattr_list_entries (2) 2026/06/09 20:16 2026/06/09 20:16 2026/06/09 21:02 c36c07f6
662933c2 assessment-security 💥 KASAN: use-after-free Read in ext4_xattr_list_entries (2) 2026/06/04 00:00 2026/06/04 00:00 2026/06/04 00:00 62fe1528
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] KASAN: use-after-free Read in ext4_xattr_list_entries (2) 0 (1) 2026/06/09 21:03
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: use-after-free Read in ext4_xattr_list_entries ext4 19 4 208d 299d 0/29 auto-obsoleted due to no activity on 2026/04/10 00:23
linux-6.1 KASAN: use-after-free Read in ext4_xattr_list_entries 19 syz, C error 15 174d 199d 0/3 upstream: reported C repro on 2026/01/18 01:47
android-6-1 KASAN: use-after-free Read in ext4_xattr_list_entries 19 syz, C 6 22d 22d 0/2 upstream: reported C repro on 2026/07/14 23:26

Sample crash report:
==================================================================
BUG: KASAN: use-after-free in ext4_xattr_list_entries+0x302/0x3d0 fs/ext4/xattr.c:724
Read of size 4 at addr ffff888052e7c014 by task syz.0.0/5330

CPU: 0 UID: 0 PID: 5330 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description+0x55/0x1e0 mm/kasan/report.c:378
 print_report+0x58/0x70 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 ext4_xattr_list_entries+0x302/0x3d0 fs/ext4/xattr.c:724
 ext4_xattr_ibody_list fs/ext4/xattr.c:793 [inline]
 ext4_listxattr+0x229/0x680 fs/ext4/xattr.c:818
 vfs_listxattr fs/xattr.c:516 [inline]
 listxattr+0x19d/0x380 fs/xattr.c:941
 filename_listxattr fs/xattr.c:974 [inline]
 path_listxattrat+0x1a3/0x3f0 fs/xattr.c:1001
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7ba719e019
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:00007f7ba8032fe8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c2
RAX: ffffffffffffffda RBX: 00007f7ba7426090 RCX: 00007f7ba719e019
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000040
RBP: 00007f7ba723500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7ba7426128 R14: 00007f7ba7426090 R15: 00007fffece08a58
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x7f7b9b11f pfn:0x52e7c
flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff)
raw: 04fff00000000000 ffffea00014ba848 ffffea00014baa08 0000000000000000
raw: 00000007f7b9b11f 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 5330, tgid 5328 (syz.0.0), ts 95093081987, free_ts 95699880197
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x1f9/0x250 mm/page_alloc.c:1859
 prep_new_page mm/page_alloc.c:1867 [inline]
 get_page_from_freelist+0x21fa/0x2270 mm/page_alloc.c:3946
 __alloc_frozen_pages_noprof+0x18d/0x380 mm/page_alloc.c:5304
 alloc_pages_mpol+0x212/0x380 mm/mempolicy.c:2490
 folio_alloc_mpol_noprof+0x39/0x160 mm/mempolicy.c:2509
 vma_alloc_folio_noprof+0xe1/0x1e0 mm/mempolicy.c:2544
 folio_prealloc mm/memory.c:-1 [inline]
 alloc_anon_folio mm/memory.c:5247 [inline]
 do_anonymous_page mm/memory.c:5342 [inline]
 do_pte_missing+0x173a/0x34b0 mm/memory.c:4564
 handle_pte_fault mm/memory.c:6379 [inline]
 __handle_mm_fault mm/memory.c:6517 [inline]
 handle_mm_fault+0x1b36/0x3080 mm/memory.c:6686
 do_user_addr_fault+0xa4d/0x1340 arch/x86/mm/fault.c:1343
 handle_page_fault arch/x86/mm/fault.c:1483 [inline]
 exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
page last free pid 5330 tgid 5328 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 __free_pages_prepare mm/page_alloc.c:1406 [inline]
 free_unref_folios+0xd84/0x14a0 mm/page_alloc.c:3011
 folios_put_refs+0x9e9/0xb30 mm/swap.c:1057
 free_pages_and_swap_cache+0x2ba/0x490 mm/swap_state.c:586
 __tlb_batch_free_encoded_pages mm/mmu_gather.c:138 [inline]
 tlb_batch_pages_flush mm/mmu_gather.c:151 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:417 [inline]
 tlb_flush_mmu+0x6d3/0xa30 mm/mmu_gather.c:424
 tlb_finish_mmu+0xf4/0x220 mm/mmu_gather.c:549
 unmap_region+0x2a5/0x330 mm/vma.c:491
 vms_clear_ptes mm/vma.c:1303 [inline]
 vms_complete_munmap_vmas+0x427/0xbe0 mm/vma.c:1345
 do_vmi_align_munmap+0x3b7/0x4b0 mm/vma.c:1604
 do_vmi_munmap+0x252/0x2d0 mm/vma.c:1652
 __vm_munmap+0x241/0x3e0 mm/vma.c:3288
 __do_sys_munmap mm/mmap.c:1079 [inline]
 __se_sys_munmap mm/mmap.c:1076 [inline]
 __x64_sys_munmap+0x60/0x70 mm/mmap.c:1076
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff888052e7bf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888052e7bf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888052e7c000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                         ^
 ffff888052e7c080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888052e7c100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/04 04:43 upstream 848acc8ffe1b 9451e17e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: use-after-free Read in ext4_xattr_list_entries
2026/07/24 02:44 upstream d326f83e819c 544adce9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: use-after-free Read in ext4_xattr_list_entries
2026/07/05 15:08 upstream 7404ce516372 fcece630 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: use-after-free Read in ext4_xattr_list_entries
2026/06/07 13:40 upstream 8e65320d91cd cc095639 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: use-after-free Read in ext4_xattr_list_entries
2026/06/02 20:37 upstream 6f3ed7fec72f 62fe1528 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: use-after-free Read in ext4_xattr_list_entries
2026/07/25 05:36 upstream e2a936998ab2 492bab15 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root KASAN: slab-use-after-free Read in ext4_xattr_list_entries
* Struck through repros no longer work on HEAD.