[syzbot] BUG: unable to handle kernel NULL pointer dereference in __lookup_slow (2)
376 views
Skip to first unread message
syzbot
Apr 13, 2021, 1:55:23 AM4/13/21
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
Hello,
syzbot found the following issue on:
HEAD commit: d93a0d43 Merge tag 'block-5.12-2021-04-02' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16519431d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=71a75beb62b62a34
dashboard link: https://syzkaller.appspot.com/bug?extid=11c49ce9d4e7896f3406
compiler: Debian clang version 11.0.1-2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+11c49c...@syzkaller.appspotmail.com
REISERFS (device loop4): Using r5 hash to sort names
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 6bb82067 P4D 6bb82067 PUD 6bb81067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11072 Comm: syz-executor.4 Not tainted 5.12.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90008f8fa20 EFLAGS: 00010246
RAX: 1ffffffff13872e8 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: 0000000000000000 RSI: ffff88802e9d9490 RDI: ffff88807f140190
RBP: ffffffff89c39740 R08: ffffffff81c9d4de R09: fffffbfff200a946
R10: fffffbfff200a946 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88807f140190 R14: 1ffff11005d3b292 R15: ffff88802e9d9490
FS: 00007f894af88700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000006bb83000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__lookup_slow+0x240/0x370 fs/namei.c:1626
lookup_one_len+0x10e/0x200 fs/namei.c:2649
reiserfs_lookup_privroot+0x85/0x1e0 fs/reiserfs/xattr.c:980
reiserfs_fill_super+0x2a69/0x3160 fs/reiserfs/super.c:2176
mount_bdev+0x26c/0x3a0 fs/super.c:1367
legacy_get_tree+0xea/0x180 fs/fs_context.c:592
vfs_get_tree+0x86/0x270 fs/super.c:1497
do_new_mount fs/namespace.c:2903 [inline]
path_mount+0x188a/0x29a0 fs/namespace.c:3233
do_mount fs/namespace.c:3246 [inline]
__do_sys_mount fs/namespace.c:3454 [inline]
__se_sys_mount+0x28c/0x320 fs/namespace.c:3431
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x46797a
Code: 48 c7 c2 bc ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f894af87fa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 000000000046797a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f894af88000
RBP: 00007f894af88040 R08: 00007f894af88040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f894af88000 R15: 0000000020011500
Modules linked in:
CR2: 0000000000000000
---[ end trace a1b8dbb111baf993 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90008f8fa20 EFLAGS: 00010246
RAX: 1ffffffff13872e8 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: 0000000000000000 RSI: ffff88802e9d9490 RDI: ffff88807f140190
RBP: ffffffff89c39740 R08: ffffffff81c9d4de R09: fffffbfff200a946
R10: fffffbfff200a946 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88807f140190 R14: 1ffff11005d3b292 R15: ffff88802e9d9490
FS: 00007f894af88700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000006bb83000 CR4: 00000000001506f0
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: d93a0d43 Merge tag 'block-5.12-2021-04-02' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16519431d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=71a75beb62b62a34
dashboard link: https://syzkaller.appspot.com/bug?extid=11c49ce9d4e7896f3406
compiler: Debian clang version 11.0.1-2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+11c49c...@syzkaller.appspotmail.com
REISERFS (device loop4): Using r5 hash to sort names
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 6bb82067 P4D 6bb82067 PUD 6bb81067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11072 Comm: syz-executor.4 Not tainted 5.12.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90008f8fa20 EFLAGS: 00010246
RAX: 1ffffffff13872e8 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: 0000000000000000 RSI: ffff88802e9d9490 RDI: ffff88807f140190
RBP: ffffffff89c39740 R08: ffffffff81c9d4de R09: fffffbfff200a946
R10: fffffbfff200a946 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88807f140190 R14: 1ffff11005d3b292 R15: ffff88802e9d9490
FS: 00007f894af88700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000006bb83000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__lookup_slow+0x240/0x370 fs/namei.c:1626
lookup_one_len+0x10e/0x200 fs/namei.c:2649
reiserfs_lookup_privroot+0x85/0x1e0 fs/reiserfs/xattr.c:980
reiserfs_fill_super+0x2a69/0x3160 fs/reiserfs/super.c:2176
mount_bdev+0x26c/0x3a0 fs/super.c:1367
legacy_get_tree+0xea/0x180 fs/fs_context.c:592
vfs_get_tree+0x86/0x270 fs/super.c:1497
do_new_mount fs/namespace.c:2903 [inline]
path_mount+0x188a/0x29a0 fs/namespace.c:3233
do_mount fs/namespace.c:3246 [inline]
__do_sys_mount fs/namespace.c:3454 [inline]
__se_sys_mount+0x28c/0x320 fs/namespace.c:3431
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x46797a
Code: 48 c7 c2 bc ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f894af87fa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 000000000046797a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f894af88000
RBP: 00007f894af88040 R08: 00007f894af88040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f894af88000 R15: 0000000020011500
Modules linked in:
CR2: 0000000000000000
---[ end trace a1b8dbb111baf993 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90008f8fa20 EFLAGS: 00010246
RAX: 1ffffffff13872e8 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: 0000000000000000 RSI: ffff88802e9d9490 RDI: ffff88807f140190
RBP: ffffffff89c39740 R08: ffffffff81c9d4de R09: fffffbfff200a946
R10: fffffbfff200a946 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88807f140190 R14: 1ffff11005d3b292 R15: ffff88802e9d9490
FS: 00007f894af88700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000006bb83000 CR4: 00000000001506f0
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Jun 27, 2021, 1:16:19 AM6/27/21
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, ph...@philpotter.co.uk, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
syzbot has found a reproducer for the following issue on:
HEAD commit: a1f92694 Add linux-next specific files for 20210518
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16935e94300000
kernel config: https://syzkaller.appspot.com/x/.config?x=d612e75ffd53a6d3
dashboard link: https://syzkaller.appspot.com/bug?extid=11c49ce9d4e7896f3406
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1477f5bfd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bded84300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+11c49c...@syzkaller.appspotmail.com
REISERFS (device loop0): journal params: device loop0, size 15748, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
RAX: dffffc0000000000 RBX: 1ffff920002c7f24 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880353f85e0 RDI: ffff888039770190
RBP: ffffffff899e4880 R08: 0000000000000000 R09: ffffffff909ffbff
R10: ffffffff81c99241 R11: 0000000000000000 R12: ffff8880353f85e0
R13: ffff888039770190 R14: ffffc9000163fa98 R15: ffffc9000163f940
FS: 000000000231e300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
lookup_one_len+0x163/0x190 fs/namei.c:2650
reiserfs_lookup_privroot+0x92/0x280 fs/reiserfs/xattr.c:980
reiserfs_fill_super+0x2124/0x2e00 fs/reiserfs/super.c:2176
mount_bdev+0x34d/0x410 fs/super.c:1368
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1498
do_new_mount fs/namespace.c:2905 [inline]
path_mount+0x132a/0x1fa0 fs/namespace.c:3235
do_mount fs/namespace.c:3248 [inline]
__do_sys_mount fs/namespace.c:3456 [inline]
__se_sys_mount fs/namespace.c:3433 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3433
do_syscall_64+0x31/0xb0 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x445b6a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 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:00007ffdfe200cf8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffdfe200d50 RCX: 0000000000445b6a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffdfe200d10
RBP: 00007ffdfe200d10 R08: 00007ffdfe200d50 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 00000000200002a8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000007
RAX: dffffc0000000000 RBX: 1ffff920002c7f24 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880353f85e0 RDI: ffff888039770190
RBP: ffffffff899e4880 R08: 0000000000000000 R09: ffffffff909ffbff
R10: ffffffff81c99241 R11: 0000000000000000 R12: ffff8880353f85e0
R13: ffff888039770190 R14: ffffc9000163fa98 R15: ffffc9000163f940
FS: 000000000231e300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
HEAD commit: a1f92694 Add linux-next specific files for 20210518
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16935e94300000
kernel config: https://syzkaller.appspot.com/x/.config?x=d612e75ffd53a6d3
dashboard link: https://syzkaller.appspot.com/bug?extid=11c49ce9d4e7896f3406
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1477f5bfd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bded84300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+11c49c...@syzkaller.appspotmail.com
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 1d164067 P4D 1d164067 PUD 143aa067 PMD 0
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8454 Comm: syz-executor105 Not tainted 5.13.0-rc2-next-20210518-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc9000163f908 EFLAGS: 00010246
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RAX: dffffc0000000000 RBX: 1ffff920002c7f24 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880353f85e0 RDI: ffff888039770190
RBP: ffffffff899e4880 R08: 0000000000000000 R09: ffffffff909ffbff
R10: ffffffff81c99241 R11: 0000000000000000 R12: ffff8880353f85e0
R13: ffff888039770190 R14: ffffc9000163fa98 R15: ffffc9000163f940
FS: 000000000231e300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000169ad000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__lookup_slow+0x24c/0x480 fs/namei.c:1629
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_one_len+0x163/0x190 fs/namei.c:2650
reiserfs_lookup_privroot+0x92/0x280 fs/reiserfs/xattr.c:980
reiserfs_fill_super+0x2124/0x2e00 fs/reiserfs/super.c:2176
mount_bdev+0x34d/0x410 fs/super.c:1368
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1498
do_new_mount fs/namespace.c:2905 [inline]
path_mount+0x132a/0x1fa0 fs/namespace.c:3235
do_mount fs/namespace.c:3248 [inline]
__do_sys_mount fs/namespace.c:3456 [inline]
__se_sys_mount fs/namespace.c:3433 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3433
do_syscall_64+0x31/0xb0 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x445b6a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 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:00007ffdfe200cf8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffdfe200d50 RCX: 0000000000445b6a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffdfe200d10
RBP: 00007ffdfe200d10 R08: 00007ffdfe200d50 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 00000000200002a8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000007
Modules linked in:
CR2: 0000000000000000
---[ end trace 23e9a8ddc3d2104a ]---
CR2: 0000000000000000
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc9000163f908 EFLAGS: 00010246
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RAX: dffffc0000000000 RBX: 1ffff920002c7f24 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880353f85e0 RDI: ffff888039770190
RBP: ffffffff899e4880 R08: 0000000000000000 R09: ffffffff909ffbff
R10: ffffffff81c99241 R11: 0000000000000000 R12: ffff8880353f85e0
R13: ffff888039770190 R14: ffffc9000163fa98 R15: ffffc9000163f940
FS: 000000000231e300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000169ad000 CR4: 00000000001506f0
syzbot
Apr 14, 2023, 6:28:35 AM4/14/23
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages