syzbot


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: 7d21h, last: 3d03h
✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision Error
3d7b2494-e9b0-4d67-bc7a-3c0b99f28dcb 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 c36c07f6c1f2230a36374cbd22235f635e8f9284
b34af3c3-3b70-47da-85aa-55b6a5daf9f2 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 c36c07f6c1f2230a36374cbd22235f635e8f9284
662933c2-3c23-461a-9119-fd68fa47a7df 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 62fe15281f5011cd203d8845b8767b10e7443aa5 failed to run ["git" "-c" "core.hooksPath=/dev/null" "fetch" "--force" "--tags" "f569e972c8e9057ee9c286220c83a480ebf30cc5" "6f3ed7fec72fc8979b2a8c7219c0a9fcfc8d07b5"]: exit status 128 error: insufficient permission for adding an object to repository database .git/objects fatal: failed to write object fatal: unpack-objects failed
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 (2)
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 151d 242d 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 C error 15 118d 143d 0/3 upstream: reported C repro on 2026/01/18 01:47

Sample crash report:
loop0: detected capacity change from 0 to 2048
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
cdc_ether 5-1:1.0: probe with driver cdc_ether failed with error -22
loop0: detected capacity change from 2048 to 64
EXT4-fs error (device loop0): xattr_find_entry:337: inode #15: comm syz.0.0: corrupted xattr entries
==================================================================
BUG: KASAN: use-after-free in ext4_xattr_list_entries+0x302/0x3d0 fs/ext4/xattr.c:724
Read of size 4 at addr ffff8880568de014 by task syz.0.0/5342

CPU: 0 UID: 0 PID: 5342 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+0x221/0x670 fs/ext4/xattr.c:818
 vfs_listxattr fs/xattr.c:511 [inline]
 listxattr+0x112/0x2a0 fs/xattr.c:933
 filename_listxattr fs/xattr.c:966 [inline]
 path_listxattrat+0x1a3/0x3f0 fs/xattr.c:993
 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:0x7f9709f9ce59
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:00007f970af29fe8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c3
RAX: ffffffffffffffda RBX: 00007f970a215fa0 RCX: 00007f9709f9ce59
RDX: 000000000000002d RSI: 0000200000000100 RDI: 0000200000000140
RBP: 00007f970a032d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f970a216038 R14: 00007f970a215fa0 R15: 00007fff4c5d5648
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x568de
flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff)
raw: 04fff00000000000 ffffea00015a37c8 ffffea000141f208 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
 ffff8880568ddf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880568ddf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880568de000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                         ^
 ffff8880568de080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8880568de100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
* Struck through repros no longer work on HEAD.