[moderation] [kernel?] BUG: unable to handle kernel paging request in map_id_range_down
0 views
Skip to first unread message
syzbot
Jun 10, 2024, 10:05:31 AMJun 10
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 2df0193e62cf Merge tag 'thermal-6.10-rc3' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1217374a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=be87a19ea07545e5c211
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2df0193e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7690676593db/vmlinux-2df0193e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f235004f189b/bzImage-2df0193e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be87a1...@syzkaller.appspotmail.com
loop3: detected capacity change from 0 to 4096
ntfs3: loop3: Different NTFS sector size (1024) and media sector size (512).
BUG: unable to handle page fault for address: ffffff8da63d8000
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD d97e067 P4D d97e067 PUD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 13474 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00097-g2df0193e62cf #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:map_id_range_down+0x8f/0x3a0 kernel/user_namespace.c:318
Code: 00 00 48 89 44 24 70 31 c0 e8 ad 1b 04 00 4c 89 f0 48 c1 e8 03 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 8b 02 00 00 4c 8b 74 24 08 <45> 8b 3e 44 89 3c 24 bf 05 00 00 00 44 89 fe e8 7d 16 04 00 41 83
RSP: 0018:ffffc900032bf798 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90006139000
RDX: 0000000000040000 RSI: ffffffff8189c943 RDI: ffffff8da63d8000
RBP: dffffc0000000000 R08: 0000000000000001 R09: ffffed100946ce5f
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffff8da63d8000 R14: ffffff8da63d8000 R15: dffffc0000000000
FS: 00007f91508b96c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8da63d8000 CR3: 0000000047b1c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
map_id_down kernel/user_namespace.c:337 [inline]
make_kuid+0x1f/0x30 kernel/user_namespace.c:414
i_uid_write include/linux/fs.h:1368 [inline]
inode_init_always+0x2f6/0xf50 fs/inode.c:174
alloc_inode+0x7d/0x230 fs/inode.c:268
iget5_locked fs/inode.c:1235 [inline]
iget5_locked+0x1c9/0x2c0 fs/inode.c:1228
ntfs_iget5+0xd1/0x3970 fs/ntfs3/inode.c:532
ntfs_fill_super+0x3738/0x4460 fs/ntfs3/super.c:1485
get_tree_bdev+0x36f/0x610 fs/super.c:1615
vfs_get_tree+0x8f/0x380 fs/super.c:1780
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f914fa7e5ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f91508b8ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f91508b8f80 RCX: 00007f914fa7e5ea
RDX: 0000000020000040 RSI: 0000000020000300 RDI: 00007f91508b8f40
RBP: 0000000020000040 R08: 00007f91508b8f80 R09: 0000000000800000
R10: 0000000000800000 R11: 0000000000000202 R12: 0000000020000300
R13: 00007f91508b8f40 R14: 000000000001f828 R15: 0000000020000640
</TASK>
Modules linked in:
CR2: ffffff8da63d8000
---[ end trace 0000000000000000 ]---
RIP: 0010:map_id_range_down+0x8f/0x3a0 kernel/user_namespace.c:318
Code: 00 00 48 89 44 24 70 31 c0 e8 ad 1b 04 00 4c 89 f0 48 c1 e8 03 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 8b 02 00 00 4c 8b 74 24 08 <45> 8b 3e 44 89 3c 24 bf 05 00 00 00 44 89 fe e8 7d 16 04 00 41 83
RSP: 0018:ffffc900032bf798 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90006139000
RDX: 0000000000040000 RSI: ffffffff8189c943 RDI: ffffff8da63d8000
RBP: dffffc0000000000 R08: 0000000000000001 R09: ffffed100946ce5f
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffff8da63d8000 R14: ffffff8da63d8000 R15: dffffc0000000000
FS: 00007f91508b96c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8da63d8000 CR3: 0000000047b1c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 00 00 add %al,(%rax)
2: 48 89 44 24 70 mov %rax,0x70(%rsp)
7: 31 c0 xor %eax,%eax
9: e8 ad 1b 04 00 call 0x41bbb
e: 4c 89 f0 mov %r14,%rax
11: 48 c1 e8 03 shr $0x3,%rax
15: 0f b6 04 28 movzbl (%rax,%rbp,1),%eax
19: 84 c0 test %al,%al
1b: 74 08 je 0x25
1d: 3c 03 cmp $0x3,%al
1f: 0f 8e 8b 02 00 00 jle 0x2b0
25: 4c 8b 74 24 08 mov 0x8(%rsp),%r14
* 2a: 45 8b 3e mov (%r14),%r15d <-- trapping instruction
2d: 44 89 3c 24 mov %r15d,(%rsp)
31: bf 05 00 00 00 mov $0x5,%edi
36: 44 89 fe mov %r15d,%esi
39: e8 7d 16 04 00 call 0x416bb
3e: 41 rex.B
3f: 83 .byte 0x83
---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 2df0193e62cf Merge tag 'thermal-6.10-rc3' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1217374a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=be87a19ea07545e5c211
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2df0193e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7690676593db/vmlinux-2df0193e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f235004f189b/bzImage-2df0193e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be87a1...@syzkaller.appspotmail.com
loop3: detected capacity change from 0 to 4096
ntfs3: loop3: Different NTFS sector size (1024) and media sector size (512).
BUG: unable to handle page fault for address: ffffff8da63d8000
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD d97e067 P4D d97e067 PUD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 13474 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00097-g2df0193e62cf #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:map_id_range_down+0x8f/0x3a0 kernel/user_namespace.c:318
Code: 00 00 48 89 44 24 70 31 c0 e8 ad 1b 04 00 4c 89 f0 48 c1 e8 03 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 8b 02 00 00 4c 8b 74 24 08 <45> 8b 3e 44 89 3c 24 bf 05 00 00 00 44 89 fe e8 7d 16 04 00 41 83
RSP: 0018:ffffc900032bf798 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90006139000
RDX: 0000000000040000 RSI: ffffffff8189c943 RDI: ffffff8da63d8000
RBP: dffffc0000000000 R08: 0000000000000001 R09: ffffed100946ce5f
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffff8da63d8000 R14: ffffff8da63d8000 R15: dffffc0000000000
FS: 00007f91508b96c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8da63d8000 CR3: 0000000047b1c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
map_id_down kernel/user_namespace.c:337 [inline]
make_kuid+0x1f/0x30 kernel/user_namespace.c:414
i_uid_write include/linux/fs.h:1368 [inline]
inode_init_always+0x2f6/0xf50 fs/inode.c:174
alloc_inode+0x7d/0x230 fs/inode.c:268
iget5_locked fs/inode.c:1235 [inline]
iget5_locked+0x1c9/0x2c0 fs/inode.c:1228
ntfs_iget5+0xd1/0x3970 fs/ntfs3/inode.c:532
ntfs_fill_super+0x3738/0x4460 fs/ntfs3/super.c:1485
get_tree_bdev+0x36f/0x610 fs/super.c:1615
vfs_get_tree+0x8f/0x380 fs/super.c:1780
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f914fa7e5ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f91508b8ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f91508b8f80 RCX: 00007f914fa7e5ea
RDX: 0000000020000040 RSI: 0000000020000300 RDI: 00007f91508b8f40
RBP: 0000000020000040 R08: 00007f91508b8f80 R09: 0000000000800000
R10: 0000000000800000 R11: 0000000000000202 R12: 0000000020000300
R13: 00007f91508b8f40 R14: 000000000001f828 R15: 0000000020000640
</TASK>
Modules linked in:
CR2: ffffff8da63d8000
---[ end trace 0000000000000000 ]---
RIP: 0010:map_id_range_down+0x8f/0x3a0 kernel/user_namespace.c:318
Code: 00 00 48 89 44 24 70 31 c0 e8 ad 1b 04 00 4c 89 f0 48 c1 e8 03 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 8b 02 00 00 4c 8b 74 24 08 <45> 8b 3e 44 89 3c 24 bf 05 00 00 00 44 89 fe e8 7d 16 04 00 41 83
RSP: 0018:ffffc900032bf798 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90006139000
RDX: 0000000000040000 RSI: ffffffff8189c943 RDI: ffffff8da63d8000
RBP: dffffc0000000000 R08: 0000000000000001 R09: ffffed100946ce5f
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffff8da63d8000 R14: ffffff8da63d8000 R15: dffffc0000000000
FS: 00007f91508b96c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8da63d8000 CR3: 0000000047b1c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 00 00 add %al,(%rax)
2: 48 89 44 24 70 mov %rax,0x70(%rsp)
7: 31 c0 xor %eax,%eax
9: e8 ad 1b 04 00 call 0x41bbb
e: 4c 89 f0 mov %r14,%rax
11: 48 c1 e8 03 shr $0x3,%rax
15: 0f b6 04 28 movzbl (%rax,%rbp,1),%eax
19: 84 c0 test %al,%al
1b: 74 08 je 0x25
1d: 3c 03 cmp $0x3,%al
1f: 0f 8e 8b 02 00 00 jle 0x2b0
25: 4c 8b 74 24 08 mov 0x8(%rsp),%r14
* 2a: 45 8b 3e mov (%r14),%r15d <-- trapping instruction
2d: 44 89 3c 24 mov %r15d,(%rsp)
31: bf 05 00 00 00 mov $0x5,%edi
36: 44 89 fe mov %r15d,%esi
39: e8 7d 16 04 00 call 0x416bb
3e: 41 rex.B
3f: 83 .byte 0x83
---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, 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