BUG: unable to handle kernel NULL pointer dereference in __lookup_hash (2)
12 views
Skip to first unread message
syzbot
May 10, 2021, 6:30:18 AM5/10/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15f80579d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=f41e5ef4b10d81a05122
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+f41e5e...@syzkaller.appspotmail.com
REISERFS (device loop1): Using tea hash to sort names
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: (null)
PGD 3f61d067 P4D 3f61d067 PUD 226ef067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 28350 Comm: syz-executor.1 Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809b9a4280 task.stack: ffff888221388000
RIP: 0010: (null)
RSP: 0018:ffff88822138fa30 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff8796bbc0 RCX: ffffc9000af0f000
RDX: 0000000000000000 RSI: ffff88808e224420 RDI: ffff888029c9f748
RBP: ffff888029c9f748 R08: 0000000000000001 R09: 0000000000000002
R10: 0000000000000000 R11: ffff88809b9a4280 R12: ffff88808e224420
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000076
FS: 00007fb9aeecd700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000912e6000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_real fs/namei.c:1555 [inline]
__lookup_hash fs/namei.c:1575 [inline]
__lookup_hash+0x1bb/0x270 fs/namei.c:1563
lookup_one_len+0x279/0x3a0 fs/namei.c:2539
reiserfs_lookup_privroot+0x92/0x270 fs/reiserfs/xattr.c:970
reiserfs_fill_super+0x1ae0/0x28c0 fs/reiserfs/super.c:2179
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x467b1a
RSP: 002b:00007fb9aeeccfa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 0000000000467b1a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fb9aeecd000
RBP: 00007fb9aeecd040 R08: 00007fb9aeecd040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fb9aeecd000 R15: 0000000020011500
Code: Bad RIP value.
RIP: (null) RSP: ffff88822138fa30
CR2: 0000000000000000
---[ end trace 004d293e2ce030f0 ]---
---
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: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15f80579d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=f41e5ef4b10d81a05122
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+f41e5e...@syzkaller.appspotmail.com
REISERFS (device loop1): Using tea hash to sort names
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: (null)
PGD 3f61d067 P4D 3f61d067 PUD 226ef067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 28350 Comm: syz-executor.1 Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809b9a4280 task.stack: ffff888221388000
RIP: 0010: (null)
RSP: 0018:ffff88822138fa30 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff8796bbc0 RCX: ffffc9000af0f000
RDX: 0000000000000000 RSI: ffff88808e224420 RDI: ffff888029c9f748
RBP: ffff888029c9f748 R08: 0000000000000001 R09: 0000000000000002
R10: 0000000000000000 R11: ffff88809b9a4280 R12: ffff88808e224420
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000076
FS: 00007fb9aeecd700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000912e6000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_real fs/namei.c:1555 [inline]
__lookup_hash fs/namei.c:1575 [inline]
__lookup_hash+0x1bb/0x270 fs/namei.c:1563
lookup_one_len+0x279/0x3a0 fs/namei.c:2539
reiserfs_lookup_privroot+0x92/0x270 fs/reiserfs/xattr.c:970
reiserfs_fill_super+0x1ae0/0x28c0 fs/reiserfs/super.c:2179
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x467b1a
RSP: 002b:00007fb9aeeccfa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 0000000000467b1a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fb9aeecd000
RBP: 00007fb9aeecd040 R08: 00007fb9aeecd040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fb9aeecd000 R15: 0000000020011500
Code: Bad RIP value.
RIP: (null) RSP: ffff88822138fa30
CR2: 0000000000000000
---[ end trace 004d293e2ce030f0 ]---
---
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
May 10, 2021, 6:50:18 AM5/10/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1065352dd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15403b45d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f41e5e...@syzkaller.appspotmail.com
reiserfs: using flush barriers
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
RIP: 0010: (null)
RSP: 0018:ffff8880a0a57a30 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff8796bbc0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88808e19fa20 RDI: ffff8880891f4748
RBP: ffff8880891f4748 R08: 0000000000000001 R09: 0000000000000002
R10: 0000000000000000 R11: ffff8880aa2fe380 R12: ffff88808e19fa20
RSP: 002b:00007ffdf1f53ac8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffdf1f53b20 RCX: 00000000004451aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffdf1f53ae0
RBP: 00007ffdf1f53ae0 R08: 00007ffdf1f53b20 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 00000000200002a8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000007
Code: Bad RIP value.
RIP: (null) RSP: ffff8880a0a57a30
CR2: 0000000000000000
---[ end trace 5d8dd39ec190a01b ]---
HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=f41e5ef4b10d81a05122
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17087779d00000
dashboard link: https://syzkaller.appspot.com/bug?extid=f41e5ef4b10d81a05122
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15403b45d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f41e5e...@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
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: (null)
PGD a9d2c067 P4D a9d2c067 PUD a9d25067 PMD 0
IP: (null)
Oops: 0010 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 7978 Comm: syz-executor021 Not tainted 4.14.232-syzkaller #0
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880aa2fe380 task.stack: ffff8880a0a50000
RIP: 0010: (null)
RSP: 0018:ffff8880a0a57a30 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff8796bbc0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88808e19fa20 RDI: ffff8880891f4748
RBP: ffff8880891f4748 R08: 0000000000000001 R09: 0000000000000002
R10: 0000000000000000 R11: ffff8880aa2fe380 R12: ffff88808e19fa20
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000076
FS: 00000000019cf300(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000aa8b0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_real fs/namei.c:1555 [inline]
__lookup_hash fs/namei.c:1575 [inline]
__lookup_hash+0x1bb/0x270 fs/namei.c:1563
lookup_one_len+0x279/0x3a0 fs/namei.c:2539
reiserfs_lookup_privroot+0x92/0x270 fs/reiserfs/xattr.c:970
reiserfs_fill_super+0x1ae0/0x28c0 fs/reiserfs/super.c:2179
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4451aa
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_real fs/namei.c:1555 [inline]
__lookup_hash fs/namei.c:1575 [inline]
__lookup_hash+0x1bb/0x270 fs/namei.c:1563
lookup_one_len+0x279/0x3a0 fs/namei.c:2539
reiserfs_lookup_privroot+0x92/0x270 fs/reiserfs/xattr.c:970
reiserfs_fill_super+0x1ae0/0x28c0 fs/reiserfs/super.c:2179
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RSP: 002b:00007ffdf1f53ac8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffdf1f53b20 RCX: 00000000004451aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffdf1f53ae0
RBP: 00007ffdf1f53ae0 R08: 00007ffdf1f53b20 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 00000000200002a8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000007
Code: Bad RIP value.
RIP: (null) RSP: ffff8880a0a57a30
CR2: 0000000000000000
---[ end trace 5d8dd39ec190a01b ]---
Reply all
Reply to author
Forward
0 new messages