lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000ac1c0605ee5b1e1b@google.com>
Date:   Sat, 26 Nov 2022 00:06:47 -0800
From:   syzbot <syzbot+1107451c16b9eb9d29e6@...kaller.appspotmail.com>
To:     akpm@...ux-foundation.org, brauner@...nel.org,
        keescook@...omium.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] kernel BUG in __hfsplus_setxattr

Hello,

syzbot found the following issue on:

HEAD commit:    0b1dcc2cf55a Merge tag 'mm-hotfixes-stable-2022-11-24' of ..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=111598ad880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ca997ea105bc6faa
dashboard link: https://syzkaller.appspot.com/bug?extid=1107451c16b9eb9d29e6
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17a3558d880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1347da4b880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8060ec729a5/disk-0b1dcc2c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/288bcf3c7e00/vmlinux-0b1dcc2c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/972187e4ca22/bzImage-0b1dcc2c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b45d6b75c2c2/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1107451c16b9eb9d29e6@...kaller.appspotmail.com

         and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
------------[ cut here ]------------
kernel BUG at fs/hfsplus/xattr.c:175!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3633 Comm: syz-executor292 Not tainted 6.1.0-rc6-syzkaller-00251-g0b1dcc2cf55a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x226c/0x2270 fs/hfsplus/xattr.c:331
Code: 07 80 c1 03 38 c1 0f 8c e1 f7 ff ff 4c 89 ff e8 ca 0a 7f ff e9 d4 f7 ff ff e8 c0 65 44 08 e8 2b 11 2a ff 0f 0b e8 24 11 2a ff <0f> 0b 66 90 55 53 89 f5 48 89 fb e8 14 11 2a ff 48 8d 7b 90 be 08
RSP: 0018:ffffc90003d1f2a0 EFLAGS: 00010293
RAX: ffffffff8262830c RBX: 0000000000010000 RCX: ffff888024dcd7c0
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003d1f748 R08: ffffffff82626a7a R09: ffffed1004ea9558
R10: ffffed1004ea9558 R11: 1ffff11004ea9557 R12: dffffc0000000000
R13: ffff8880281fa038 R14: 0000000000000001 R15: 1ffff1100503f407
FS:  000055555558e300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7649dcf5f0 CR3: 0000000074aad000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 hfsplus_initxattrs+0x15c/0x230 fs/hfsplus/xattr_security.c:59
 security_inode_init_security+0x3bf/0x3f0 security/security.c:1119
 hfsplus_mknod+0x1bd/0x290 fs/hfsplus/dir.c:498
 lookup_open fs/namei.c:3413 [inline]
 open_last_lookups fs/namei.c:3481 [inline]
 path_openat+0x12e2/0x2e00 fs/namei.c:3711
 do_filp_open+0x275/0x500 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_openat fs/open.c:1342 [inline]
 __se_sys_openat fs/open.c:1337 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1337
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7649dcf7a9
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:00007ffc008516c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7649dcf7a9
RDX: 00000000000026e1 RSI: 00000000200000c0 RDI: 00000000ffffff9c
RBP: 00007f7649d8f040 R08: 00000000000005eb R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7649d8f0d0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x226c/0x2270 fs/hfsplus/xattr.c:331
Code: 07 80 c1 03 38 c1 0f 8c e1 f7 ff ff 4c 89 ff e8 ca 0a 7f ff e9 d4 f7 ff ff e8 c0 65 44 08 e8 2b 11 2a ff 0f 0b e8 24 11 2a ff <0f> 0b 66 90 55 53 89 f5 48 89 fb e8 14 11 2a ff 48 8d 7b 90 be 08
RSP: 0018:ffffc90003d1f2a0 EFLAGS: 00010293
RAX: ffffffff8262830c RBX: 0000000000010000 RCX: ffff888024dcd7c0
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003d1f748 R08: ffffffff82626a7a R09: ffffed1004ea9558
R10: ffffed1004ea9558 R11: 1ffff11004ea9557 R12: dffffc0000000000
R13: ffff8880281fa038 R14: 0000000000000001 R15: 1ffff1100503f407
FS:  000055555558e300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7649dcf5f0 CR3: 0000000074aad000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

Powered by blists - more mailing lists