Hello,
syzbot found the following issue on:
HEAD commit: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=160b9949580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link:
https://syzkaller.appspot.com/bug?extid=5bde7e801f46da43adc6
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7cd9b1875376/disk-e4f7d8be.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/4b5d35d18c31/vmlinux-e4f7d8be.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/d5ee64c2af77/Image-e4f7d8be.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+5bde7e...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4934 at crypto/rsa-pkcs1pad.c:540 pkcs1pad_verify+0x454/0x5ac crypto/rsa-pkcs1pad.c:540
Modules linked in:
CPU: 1 PID: 4934 Comm: syz.0.204 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/07/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : pkcs1pad_verify+0x454/0x5ac crypto/rsa-pkcs1pad.c:540
lr : pkcs1pad_verify+0x454/0x5ac crypto/rsa-pkcs1pad.c:540
sp : ffff8000216e7630
x29: ffff8000216e7640 x28: ffff0000f54a3000 x27: ffff0000d0d15600
x26: ffff0000d0d15600 x25: ffff8000216e77c0 x24: dfff800000000000
x23: ffff8000216e79a0 x22: 0000000000000000 x21: ffff0000f54a3038
x20: 0000000000000200 x19: ffff0000f54a3000 x18: 1fffe00033e7697e
x17: ffff80000a76afc4 x16: ffff800011b90080 x15: 8a8992b545d160b9
x14: 0000000000000002 x13: 1ffff000042dceed x12: 0000000000080000
x11: 000000000000545e x10: ffff8000219ea000 x9 : ffff80000a6632a8
x8 : 000000000000545f x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000008 x3 : 0000000000000000
x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
pkcs1pad_verify+0x454/0x5ac crypto/rsa-pkcs1pad.c:540
crypto_akcipher_verify include/crypto/akcipher.h:370 [inline]
public_key_verify_signature+0x720/0xb30 crypto/asymmetric_keys/public_key.c:460
public_key_verify_signature_2+0x48/0x58 crypto/asymmetric_keys/public_key.c:479
verify_signature+0xe8/0x108 crypto/asymmetric_keys/signature.c:154
asymmetric_key_verify_signature+0x154/0x1ec crypto/asymmetric_keys/asymmetric_type.c:614
keyctl_pkey_verify+0x1c4/0x248 security/keys/keyctl_pkey.c:326
__do_sys_keyctl security/keys/keyctl.c:2017 [inline]
__se_sys_keyctl security/keys/keyctl.c:1886 [inline]
__arm64_sys_keyctl+0x62c/0x8e0 security/keys/keyctl.c:1886
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 1084
hardirqs last enabled at (1083): [<ffff800011c77b24>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (1083): [<ffff800011c77b24>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (1084): [<ffff800011b8c2bc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (914): [<ffff800008031254>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (912): [<ffff800008031220>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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