[v6.1] WARNING in emulate_vsyscall

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1771ee15180000
kernel config: https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link: https://syzkaller.appspot.com/bug?extid=adc0a92b543b3a46471b
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/73d2a8622b6e/disk-34738586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7bc2e0101a7/vmlinux-34738586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b96d1168608/bzImage-34738586.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 10704 at arch/x86/entry/vsyscall/vsyscall_64.c:278 emulate_vsyscall+0xf3d/0x1240
Modules linked in:
CPU: 0 PID: 10704 Comm: syz-executor.2 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:emulate_vsyscall+0xf3d/0x1240 arch/x86/entry/vsyscall/vsyscall_64.c:277
Code: 24 10 49 c7 c0 c0 51 e0 8a 4c 8b 4c 24 08 41 ff 36 41 54 55 41 55 53 e8 ca 90 87 09 48 83 c4 28 e9 8f fe ff ff e8 03 03 8a 00 <0f> 0b e9 83 fe ff ff 48 c7 c1 80 eb f9 8c 80 e1 07 80 c1 03 38 c1
RSP: 0000:ffffc900057cfe68 EFLAGS: 00010293
RAX: ffffffff810083ed RBX: 0000000000000100 RCX: ffff888058ea8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff810081df R09: fffffbfff1ce6d46
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100b1d531a
R13: ffffc900057cff58 R14: 0000000000000000 R15: 1ffff92000af9ffe
FS: 00007fae2b0d96c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000019 CR3: 000000005fbf1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
do_user_addr_fault arch/x86/mm/fault.c:1337 [inline]
handle_page_fault arch/x86/mm/fault.c:1462 [inline]
exc_page_fault+0x154/0x660 arch/x86/mm/fault.c:1518
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:_end+0x6d3da000/0x0
Code: Unable to access opcode bytes at 0xffffffffff5fffd6.
RSP: 002b:00007fae2b0d8b38 EFLAGS: 00010246
RAX: ffffffffffffffda RBX: 00007fae2a3abf80 RCX: 00007fae2a27de69
RDX: 00007fae2b0d8b40 RSI: 00007fae2b0d8c70 RDI: 0000000000000019
RBP: 00007fae2a2ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fae2a3abf80 R15: 00007ffc22aeb2a8
</TASK>


---
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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=11018b3d180000

kernel config: https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link: https://syzkaller.appspot.com/bug?extid=adc0a92b543b3a46471b
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=17bd7c75180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d59fe3180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/73d2a8622b6e/disk-34738586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7bc2e0101a7/vmlinux-34738586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b96d1168608/bzImage-34738586.xz

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

------------[ cut here ]------------

WARNING: CPU: 1 PID: 5324 at arch/x86/entry/vsyscall/vsyscall_64.c:278 emulate_vsyscall+0xf3d/0x1240
Modules linked in:
CPU: 1 PID: 5324 Comm: syz-executor257 Not tainted 6.1.84-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:emulate_vsyscall+0xf3d/0x1240 arch/x86/entry/vsyscall/vsyscall_64.c:277
Code: 24 10 49 c7 c0 c0 51 e0 8a 4c 8b 4c 24 08 41 ff 36 41 54 55 41 55 53 e8 ca 90 87 09 48 83 c4 28 e9 8f fe ff ff e8 03 03 8a 00 <0f> 0b e9 83 fe ff ff 48 c7 c1 80 eb f9 8c 80 e1 07 80 c1 03 38 c1

RSP: 0018:ffffc90003eafe68 EFLAGS: 00010293
RAX: ffffffff810083ed RBX: 0000000000000100 RCX: ffff8880676b3b80

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff810081df R09: fffffbfff1ce6d46

R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100ced6a8a
R13: ffffc90003eaff58 R14: 0000000000000000 R15: 1ffff920007d5ffe
FS: 00007f9b61f386c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000000000000019 CR3: 0000000076bb7000 CR4: 00000000003526e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
do_user_addr_fault arch/x86/mm/fault.c:1337 [inline]
handle_page_fault arch/x86/mm/fault.c:1462 [inline]
exc_page_fault+0x154/0x660 arch/x86/mm/fault.c:1518
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:_end+0x6d3da000/0x0
Code: Unable to access opcode bytes at 0xffffffffff5fffd6.

RSP: 002b:00007f9b61f37bb8 EFLAGS: 00010246
RAX: ffffffffffffffda RBX: 0000000000000040 RCX: 00007f9b62788b59
RDX: 00007f9b61f37bc0 RSI: 00007f9b61f37cf0 RDI: 0000000000000019
RBP: 0400000000000000 R08: 00007f9b61f386c0 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000246 R12: 00007f9b628131ec
R13: 0000000000000016 R14: 00007fffc77a4c10 R15: 00007fffc77a4cf8
</TASK>


---
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.