[v5.15] Internal error in futex_requeue

3 views
Skip to first unread message

syzbot

unread,
Aug 8, 2025, 10:58:36 AM8/8/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17cd3ea2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=ae7dd8fc6599d0b4f52b
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4604 Comm: syz.1.219 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : get_futex_value_locked kernel/futex/core.c:793 [inline]
pc : futex_requeue+0x5ac/0x1838 kernel/futex/core.c:2226
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:239 [inline]
lr : get_futex_value_locked kernel/futex/core.c:790 [inline]
lr : futex_requeue+0x588/0x1838 kernel/futex/core.c:2226
sp : ffff80001fe776e0
x29: ffff80001fe77840 x28: 1fffe0001816cce1 x27: ffff0000c0b66708
x26: dfff800000000000 x25: ffff0000c0b651e4 x24: 0000000000000000
x23: 1fffe0001816ca3c x22: ffff0000c0b651c0 x21: 0000000000000060
x20: ffff0000c0d30000 x19: 00000000fffffff2 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000083c25fc x15: 00000000ec9da11a
x14: 00000000a1a6fffe x13: 1ffff0000282e06b x12: 0000000000080000
x11: 0000ffffffffffff x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff8000083c24d8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d608c
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
get_futex_value_locked kernel/futex/core.c:790 [inline]
futex_requeue+0x5ac/0x1838 kernel/futex/core.c:2226
do_futex+0xb88/0x257c kernel/futex/core.c:-1
__do_sys_futex kernel/futex/core.c:4059 [inline]
__se_sys_futex kernel/futex/core.c:4040 [inline]
__arm64_sys_futex+0x388/0x400 kernel/futex/core.c:4040
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f b94083e0 2a0003f3 b8400918 (2a1303e1)
---[ end trace 55d34b57878d15e0 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: b94083e0 ldr w0, [sp, #128]
8: 2a0003f3 mov w19, w0
c: b8400918 ldtr w24, [x8]
* 10: 2a1303e1 mov w1, w19 <-- trapping instruction


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

unread,
Aug 10, 2025, 6:34:38 AM8/10/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13b9b1a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=ae7dd8fc6599d0b4f52b
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122a49a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bb3434580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4182 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : get_futex_value_locked kernel/futex/core.c:793 [inline]
pc : futex_requeue+0x5ac/0x1838 kernel/futex/core.c:2226
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:239 [inline]
lr : get_futex_value_locked kernel/futex/core.c:790 [inline]
lr : futex_requeue+0x588/0x1838 kernel/futex/core.c:2226
sp : ffff80001fb676e0
x29: ffff80001fb67840 x28: 1fffe0001aabece1 x27: ffff0000d55f6708
x26: dfff800000000000 x25: ffff0000d55f51e4 x24: 0000000000000000
x23: 1fffe0001aabea3c x22: ffff0000d55f51c0 x21: 0000000000000196
x20: ffff0000c0d30000 x19: 00000000fffffff2 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000083c25fc x15: 00000000f88c139e
x14: 000000009bdb1a0a x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000ffffffffffff x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff8000083c24d8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d608c
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
get_futex_value_locked kernel/futex/core.c:790 [inline]
futex_requeue+0x5ac/0x1838 kernel/futex/core.c:2226
do_futex+0xb88/0x257c kernel/futex/core.c:-1
__do_sys_futex kernel/futex/core.c:4059 [inline]
__se_sys_futex kernel/futex/core.c:4040 [inline]
__arm64_sys_futex+0x388/0x400 kernel/futex/core.c:4040
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f b94083e0 2a0003f3 b8400918 (2a1303e1)
---[ end trace 9e36975f8edcd082 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: b94083e0 ldr w0, [sp, #128]
8: 2a0003f3 mov w19, w0
c: b8400918 ldtr w24, [x8]
* 10: 2a1303e1 mov w1, w19 <-- trapping instruction


---
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.
Reply all
Reply to author
Forward
0 new messages