[syzbot] [kernel?] kernel BUG in __jump_label_patch

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f76698bd9a8c Add linux-next specific files for 20240621
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=174ca546980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ca79e3c3b9118bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=03cfa0c5a0bcba3bf195
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1053f741980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b7883e980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f204c5d02251/disk-f76698bd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/50289c7e8999/vmlinux-f76698bd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c360e133a94f/bzImage-f76698bd.xz

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

jump_label: Fatal kernel bug, unexpected op at preempt_notifier_register+0x10/0xe0 kernel/sched/core.c:4788 [ffffffff81639840] (eb 12 90 48 c7 != 66 90 0f 1f 00)) size:2 type:1
------------[ cut here ]------------
kernel BUG at arch/x86/kernel/jump_label.c:73!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 28186 Comm: syz-executor226 Not tainted 6.10.0-rc4-next-20240621-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__jump_label_patch+0x463/0x490 arch/x86/kernel/jump_label.c:73
Code: e8 52 ae 5f 00 48 c7 c7 e0 41 c5 8b 48 8b 0c 24 48 89 ce 48 89 ca 4d 89 e8 4c 8b 4c 24 08 41 54 e8 a2 a1 56 0a 48 83 c4 08 90 <0f> 0b e8 96 9b 59 0a e8 21 ae 5f 00 90 0f 0b e8 19 ae 5f 00 90 0f
RSP: 0018:ffffc9000a7ff620 EFLAGS: 00010292
RAX: 0000000000000097 RBX: 0000000000000085 RCX: 1a06c80092f08800
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000a7ff748 R08: ffffffff81739789 R09: 1ffff920014ffe60
R10: dffffc0000000000 R11: fffff520014ffe61 R12: 0000000000000001
R13: ffffffff8bc56001 R14: ffffffff929c38a0 R15: ffffffff8bc56001
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055558d6acce8 CR3: 000000002b0e8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
arch_jump_label_transform_queue+0x68/0x100 arch/x86/kernel/jump_label.c:137
__jump_label_update+0x177/0x3a0 kernel/jump_label.c:493
__static_key_slow_dec_cpuslocked+0x250/0x410 kernel/jump_label.c:293
__static_key_slow_dec kernel/jump_label.c:301 [inline]
static_key_slow_dec+0x51/0xa0 kernel/jump_label.c:316
kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1364 [inline]
kvm_put_kvm+0xf3b/0x1300 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1388
kvm_vm_release+0x46/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1411
__fput+0x24a/0x8a0 fs/file_table.c:422
task_work_run+0x24f/0x310 kernel/task_work.c:180
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa27/0x28e0 kernel/exit.c:876
do_group_exit+0x207/0x2c0 kernel/exit.c:1025
get_signal+0x16a1/0x1740 kernel/signal.c:2909
arch_do_signal_or_restart+0x96/0x830 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xc9/0x370 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:0x7f6bcd95a559
Code: Unable to access opcode bytes at 0x7f6bcd95a52f.
RSP: 002b:00007f6bcd915228 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007f6bcd9e4328 RCX: 00007f6bcd95a559
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007f6bcd9e432c
RBP: 00007f6bcd9e4320 R08: 00007f6bcd9156c0 R09: 00007f6bcd9156c0
R10: 00007f6bcd9156c0 R11: 0000000000000246 R12: 00007f6bcd9e432c
R13: 00007f6bcd9b1074 R14: 6d766b2f7665642f R15: 00007ffd999e9ad8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__jump_label_patch+0x463/0x490 arch/x86/kernel/jump_label.c:73
Code: e8 52 ae 5f 00 48 c7 c7 e0 41 c5 8b 48 8b 0c 24 48 89 ce 48 89 ca 4d 89 e8 4c 8b 4c 24 08 41 54 e8 a2 a1 56 0a 48 83 c4 08 90 <0f> 0b e8 96 9b 59 0a e8 21 ae 5f 00 90 0f 0b e8 19 ae 5f 00 90 0f
RSP: 0018:ffffc9000a7ff620 EFLAGS: 00010292
RAX: 0000000000000097 RBX: 0000000000000085 RCX: 1a06c80092f08800
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000a7ff748 R08: ffffffff81739789 R09: 1ffff920014ffe60
R10: dffffc0000000000 R11: fffff520014ffe61 R12: 0000000000000001
R13: ffffffff8bc56001 R14: ffffffff929c38a0 R15: ffffffff8bc56001
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055558d6acce8 CR3: 000000002b0e8000 CR4: 00000000003526f0
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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