| 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
| ||
|
Message-ID: <676a86b3.050a0220.2f3838.0186.GAE@google.com> Date: Tue, 24 Dec 2024 02:02:27 -0800 From: syzbot <syzbot+346663d300c952d92718@...kaller.appspotmail.com> To: linux-kernel@...r.kernel.org, luto@...nel.org, peterz@...radead.org, syzkaller-bugs@...glegroups.com, tglx@...utronix.de Subject: [syzbot] [kernel?] BUG: unable to handle kernel paging request in sched_mm_cid_exit_signals Hello, syzbot found the following issue on: HEAD commit: 8faabc041a00 Merge tag 'net-6.13-rc4' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1181cf30580000 kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f dashboard link: https://syzkaller.appspot.com/bug?extid=346663d300c952d92718 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/ae9784e087ec/disk-8faabc04.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/30d1a89f3de0/vmlinux-8faabc04.xz kernel image: https://storage.googleapis.com/syzbot-assets/1b7c69b1e12a/bzImage-8faabc04.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+346663d300c952d92718@...kaller.appspotmail.com BUG: unable to handle page fault for address: fffffbfff3f8171b #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 23ffe4067 P4D 23ffe4067 PUD 23ffe3067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 1 UID: 0 PID: 6906 Comm: syz.3.238 Not tainted 6.13.0-rc3-syzkaller-00136-g8faabc041a00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline] RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline] RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline] RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline] RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline] RIP: 0010:kasan_check_range+0x82/0x290 mm/kasan/generic.c:189 Code: 01 00 00 00 00 fc ff df 4f 8d 3c 31 4c 89 fd 4c 29 dd 48 83 fd 10 7f 29 48 85 ed 0f 84 3e 01 00 00 4c 89 cd 48 f7 d5 48 01 dd <41> 80 3b 00 0f 85 c9 01 00 00 49 ff c3 48 ff c5 75 ee e9 1e 01 00 RSP: 0018:ffffc9000488f640 EFLAGS: 00010086 RAX: 000000000172ce01 RBX: 1ffffffff3f8171b RCX: ffffffff817ac184 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9fc0b8d8 RBP: ffffffffffffffff R08: ffffffff9fc0b8df R09: 1ffffffff3f8171b R10: dffffc0000000000 R11: fffffbfff3f8171b R12: ffff88802f3aa8c4 R13: ffff88802f3a9e00 R14: dffffc0000000001 R15: fffffbfff3f8171c FS: 00007feac63456c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff3f8171b CR3: 0000000034ab4000 CR4: 0000000000350ef0 Call Trace: <TASK> instrument_atomic_read include/linux/instrumented.h:68 [inline] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] __lock_acquire+0xc94/0x2100 kernel/locking/lockdep.c:5196 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378 raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:606 raw_spin_rq_lock kernel/sched/sched.h:1523 [inline] _raw_spin_rq_lock_irqsave kernel/sched/sched.h:1543 [inline] rq_lock_irqsave kernel/sched/sched.h:1808 [inline] class_rq_lock_irqsave_constructor kernel/sched/sched.h:1857 [inline] sched_mm_cid_exit_signals+0x17b/0x4b0 kernel/sched/core.c:10606 exit_signals+0x357/0x5c0 kernel/signal.c:3111 do_exit+0x6b4/0x28e0 kernel/exit.c:895 do_group_exit+0x207/0x2c0 kernel/exit.c:1087 get_signal+0x16b2/0x1750 kernel/signal.c:3017 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0xce/0x340 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7feac5585d29 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007feac63450e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: fffffffffffffe00 RBX: 00007feac5776088 RCX: 00007feac5585d29 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007feac5776088 RBP: 00007feac5776080 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007feac577608c R13: 0000000000000000 R14: 00007fff25f56f80 R15: 00007fff25f57068 </TASK> Modules linked in: CR2: fffffbfff3f8171b ---[ end trace 0000000000000000 ]--- RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline] RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline] RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline] RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline] RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline] RIP: 0010:kasan_check_range+0x82/0x290 mm/kasan/generic.c:189 Code: 01 00 00 00 00 fc ff df 4f 8d 3c 31 4c 89 fd 4c 29 dd 48 83 fd 10 7f 29 48 85 ed 0f 84 3e 01 00 00 4c 89 cd 48 f7 d5 48 01 dd <41> 80 3b 00 0f 85 c9 01 00 00 49 ff c3 48 ff c5 75 ee e9 1e 01 00 RSP: 0018:ffffc9000488f640 EFLAGS: 00010086 RAX: 000000000172ce01 RBX: 1ffffffff3f8171b RCX: ffffffff817ac184 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9fc0b8d8 RBP: ffffffffffffffff R08: ffffffff9fc0b8df R09: 1ffffffff3f8171b R10: dffffc0000000000 R11: fffffbfff3f8171b R12: ffff88802f3aa8c4 R13: ffff88802f3a9e00 R14: dffffc0000000001 R15: fffffbfff3f8171c FS: 00007feac63456c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff3f8171b CR3: 0000000034ab4000 CR4: 0000000000350ef0 ---------------- Code disassembly (best guess), 7 bytes skipped: 0: df 4f 8d fisttps -0x73(%rdi) 3: 3c 31 cmp $0x31,%al 5: 4c 89 fd mov %r15,%rbp 8: 4c 29 dd sub %r11,%rbp b: 48 83 fd 10 cmp $0x10,%rbp f: 7f 29 jg 0x3a 11: 48 85 ed test %rbp,%rbp 14: 0f 84 3e 01 00 00 je 0x158 1a: 4c 89 cd mov %r9,%rbp 1d: 48 f7 d5 not %rbp 20: 48 01 dd add %rbx,%rbp * 23: 41 80 3b 00 cmpb $0x0,(%r11) <-- trapping instruction 27: 0f 85 c9 01 00 00 jne 0x1f6 2d: 49 ff c3 inc %r11 30: 48 ff c5 inc %rbp 33: 75 ee jne 0x23 35: e9 .byte 0xe9 36: 1e (bad) 37: 01 00 add %eax,(%rax) --- 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. 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
Powered by blists - more mailing lists