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>] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000081dba605f19d42dd@google.com>
Date:   Fri, 06 Jan 2023 11:16:51 -0800
From:   syzbot <syzbot+b2c969f18c4ab30419f9@...kaller.appspotmail.com>
To:     jack@...e.cz, linux-kernel@...r.kernel.org,
        reiserfs-devel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        yijiangshan@...inos.cn
Subject: [syzbot] [reiserfs?] kernel BUG in reiserfs_cut_from_item

Hello,

syzbot found the following issue on:

HEAD commit:    88603b6dc419 Linux 6.2-rc2
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14fd0692480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9babfdc3dd4772d0
dashboard link: https://syzkaller.appspot.com/bug?extid=b2c969f18c4ab30419f9
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=14edd048480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13a5c50c480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a44a84e5e4e6/disk-88603b6d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df723f71c09d/vmlinux-88603b6d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3db040a6ceef/bzImage-88603b6d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2b27b4df465f/mount_0.gz

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

1:  ".."           1              2              0              2              (VISIBLE)
-------------------------------------------------------------------------------
| 5| *3.6* [2 6 0x0 SD], item_len 44, item_location 340, free_space(entry_count) 65535 |
	mode | size | nlinks | first direct | mtime
	0100000 |     24 |  1 | 0 | 1672687496
===================================================================
REISERFS panic (device loop0): PAP-5580 reiserfs_cut_from_item: item to convert does not exist ([2 6 0x1 IND])
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5065 Comm: syz-executor364 Not tainted 6.2.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__reiserfs_panic+0x12f/0x140 fs/reiserfs/prints.c:390
Code: c0 50 03 8b 48 0f 44 c8 48 0f 44 d8 48 c7 c7 80 51 03 8b 4c 89 fe 48 89 da 4d 89 f0 49 c7 c1 40 46 16 92 31 c0 e8 01 ec 82 08 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41
RSP: 0018:ffffc90003c0f140 EFLAGS: 00010246
RAX: 000000000000006e RBX: ffffffff8b0376e0 RCX: bc42c5d171a4b400
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003c0f230 R08: ffffffff816f2c9d R09: fffff52000781de1
R10: fffff52000781de1 R11: 1ffff92000781de0 R12: ffffffff8b037700
R13: ffffc90003c0f160 R14: ffffffff8cc71f98 R15: ffff888079d1a6a8
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f2c5ae6c40 CR3: 0000000021dc5000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 reiserfs_cut_from_item+0x219d/0x25b0 fs/reiserfs/stree.c:1729
 reiserfs_do_truncate+0x9d6/0x15a0 fs/reiserfs/stree.c:1973
 reiserfs_truncate_file+0x471/0x790 fs/reiserfs/inode.c:2310
 reiserfs_file_release+0x887/0xa30 fs/reiserfs/file.c:109
 __fput+0x3ba/0x880 fs/file_table.c:320
 task_work_run+0x243/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x644/0x2150 kernel/exit.c:867
 do_group_exit+0x1fd/0x2b0 kernel/exit.c:1012
 __do_sys_exit_group kernel/exit.c:1023 [inline]
 __se_sys_exit_group kernel/exit.c:1021 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1021
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6be3efd489
Code: Unable to access opcode bytes at 0x7f6be3efd45f.
RSP: 002b:00007ffec10dfdd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f6be3f72350 RCX: 00007f6be3efd489
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6be3f72350
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__reiserfs_panic+0x12f/0x140 fs/reiserfs/prints.c:390
Code: c0 50 03 8b 48 0f 44 c8 48 0f 44 d8 48 c7 c7 80 51 03 8b 4c 89 fe 48 89 da 4d 89 f0 49 c7 c1 40 46 16 92 31 c0 e8 01 ec 82 08 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41
RSP: 0018:ffffc90003c0f140 EFLAGS: 00010246
RAX: 000000000000006e RBX: ffffffff8b0376e0 RCX: bc42c5d171a4b400
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003c0f230 R08: ffffffff816f2c9d R09: fffff52000781de1
R10: fffff52000781de1 R11: 1ffff92000781de0 R12: ffffffff8b037700
R13: ffffc90003c0f160 R14: ffffffff8cc71f98 R15: ffff888079d1a6a8
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f2c5ae6c40 CR3: 0000000021dc5000 CR4: 00000000003506e0
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ