[Android 5.10] general protection fault in ext4_xattr_set_entry (4)

6 views
Skip to first unread message

syzbot

unread,
May 9, 2023, 11:48:08 AM5/9/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3ad342cf5b2c Revert "net: mdio: fix owner field for mdio b..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=119e8eea280000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c2e555eed123787
dashboard link: https://syzkaller.appspot.com/bug?extid=04ad69fe1dc2185ff324
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15af7d24280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15249a50280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/68efc541dcd2/disk-3ad342cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1c55bff052a/vmlinux-3ad342cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/62b39d17209d/bzImage-3ad342cf.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/26483f803748/mount_0.gz

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

EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue
general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 PID: 289 Comm: syz-executor335 Not tainted 5.10.177-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:ext4_xattr_set_entry+0x498/0x3960 fs/ext4/xattr.c:1616
Code: 24 78 48 89 d8 48 c1 e8 03 48 89 84 24 28 01 00 00 42 80 3c 38 00 74 08 48 89 df e8 e2 b3 ba ff 4c 8b 23 4c 89 e0 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 d1 2e 00 00 4c 89 e8 48 2b 44 24 20 48
RSP: 0018:ffffc90000af6f20 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffc90000af7320 RCX: ffff8881194a4f00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000001c
RBP: ffffc90000af71c0 R08: ffffffff81ecc504 R09: ffffed102379eb1e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 000000000000001c R15: dffffc0000000000
FS: 00005555572ea300(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561c115a9280 CR3: 000000011e4ab000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_xattr_ibody_set+0x7c/0x2b0 fs/ext4/xattr.c:2253
ext4_xattr_set_handle+0xc26/0x14e0 fs/ext4/xattr.c:2410
ext4_initxattrs+0xa7/0x120 fs/ext4/xattr_security.c:43
security_inode_init_security+0x252/0x390 security/security.c:1033
ext4_init_security+0x34/0x40 fs/ext4/xattr_security.c:57
__ext4_new_inode+0x3159/0x3f70 fs/ext4/ialloc.c:1319
ext4_create+0x267/0x530 fs/ext4/namei.c:2770
lookup_open fs/namei.c:3253 [inline]
open_last_lookups fs/namei.c:3323 [inline]
path_openat+0x1377/0x3000 fs/namei.c:3512
do_filp_open+0x21c/0x460 fs/namei.c:3542
do_sys_openat2+0x13f/0x6e0 fs/open.c:1217
do_sys_open fs/open.c:1233 [inline]
__do_sys_creat fs/open.c:1307 [inline]
__se_sys_creat fs/open.c:1301 [inline]
__x64_sys_creat+0x11f/0x160 fs/open.c:1301
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fa8f09de7a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe8fb90f18 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 33921e5989711fe9 RCX: 00007fa8f09de7a9
RDX: 00007fa8f099ce23 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007fa8f099e040 R08: 0000000000000475 R09: 0000000000000000
R10: 00007ffe8fb90de0 R11: 0000000000000246 R12: 00007fa8f099e0d0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace df8f863754cf6a3a ]---
RIP: 0010:ext4_xattr_set_entry+0x498/0x3960 fs/ext4/xattr.c:1616
Code: 24 78 48 89 d8 48 c1 e8 03 48 89 84 24 28 01 00 00 42 80 3c 38 00 74 08 48 89 df e8 e2 b3 ba ff 4c 8b 23 4c 89 e0 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 d1 2e 00 00 4c 89 e8 48 2b 44 24 20 48
RSP: 0018:ffffc90000af6f20 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffc90000af7320 RCX: ffff8881194a4f00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000001c
RBP: ffffc90000af71c0 R08: ffffffff81ecc504 R09: ffffed102379eb1e
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 000000000000001c R15: dffffc0000000000
FS: 00005555572ea300(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561c115b3de8 CR3: 000000011e4ab000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 24 78 and $0x78,%al
2: 48 89 d8 mov %rbx,%rax
5: 48 c1 e8 03 shr $0x3,%rax
9: 48 89 84 24 28 01 00 mov %rax,0x128(%rsp)
10: 00
11: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1)
16: 74 08 je 0x20
18: 48 89 df mov %rbx,%rdi
1b: e8 e2 b3 ba ff callq 0xffbab402
20: 4c 8b 23 mov (%rbx),%r12
23: 4c 89 e0 mov %r12,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 38 movzbl (%rax,%r15,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 d1 2e 00 00 jne 0x2f08
37: 4c 89 e8 mov %r13,%rax
3a: 48 2b 44 24 20 sub 0x20(%rsp),%rax
3f: 48 rex.W


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

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

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages