linux-kernel - [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <000000000000ff304105f4d1cd36@google.com>
Date:   Thu, 16 Feb 2023 06:13:44 -0800
From:   syzbot <syzbot+dac365e3ce07c3d0e496@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after_hwframe

Hello,

syzbot found the following issue on:

HEAD commit:    9d9019bcea1a Add linux-next specific files for 20230215
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=144edcc8c80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a64cbb8ad0da425e
dashboard link: https://syzkaller.appspot.com/bug?extid=dac365e3ce07c3d0e496
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/70f0c6bb5351/disk-9d9019bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7eed8686df34/vmlinux-9d9019bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84bb6da6b00e/bzImage-9d9019bc.xz

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

WARNING: can't access registers at entry_SYSCALL_64_after_hwframe+0x63/0xcd


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