[v5.15] Internal error in prctl_get_tid_address

[syzbot]

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=103f4ba2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=958df09d17418a667d22
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+958df0...@syzkaller.appspotmail.com

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4554 Comm: syz.4.66 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 : prctl_get_tid_address+0x124/0x160 kernel/sys.c:-1
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : prctl_get_tid_address+0xec/0x160 kernel/sys.c:2258
sp : ffff800020397c70
x29: ffff800020397c80 x28: ffff0000c21f3680 x27: ffff800020397cc0
x26: 1ffff00004072f98 x25: dfff800000000000 x24: 0000000000400040
x23: 0000000000ffff00 x22: dfff800000000000 x21: 000000000000ffff
x20: ffff0000c21f3ce0 x19: 000000000000ffff x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000081e1de8 x15: 000000000000003d
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 1fffe0001843e79c x9 : 0000ffffffffffff
x8 : 0000ffffa27e5430 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 00000000fffffff2
Call trace:
prctl_get_tid_address+0x124/0x160 kernel/sys.c:2258
__do_sys_prctl kernel/sys.c:2445 [inline]
__se_sys_prctl kernel/sys.c:2298 [inline]
__arm64_sys_prctl+0x270/0xf14 kernel/sys.c:2298
__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: 94196b82 2a1f03e0 f9400288 f8000aa8 (14000003)
---[ end trace c4c8225b63c7ac6a ]---
----------------
Code disassembly (best guess):
0: 94196b82 bl 0x65ae08
4: 2a1f03e0 mov w0, wzr
8: f9400288 ldr x8, [x20]
c: f8000aa8 sttr x8, [x21]
* 10: 14000003 b 0x1c <-- 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]

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=1720cba2580000

kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=958df09d17418a667d22
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=14696ba2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b106f0580000

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+958df0...@syzkaller.appspotmail.com

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:

CPU: 0 PID: 4224 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 : prctl_get_tid_address+0x124/0x160 kernel/sys.c:-1
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : prctl_get_tid_address+0xec/0x160 kernel/sys.c:2258

sp : ffff80001f887c70
x29: ffff80001f887c80 x28: ffff0000d432b680 x27: ffff80001f887cc0
x26: 1ffff00003f10f98 x25: dfff800000000000 x24: 0000000000400040

x23: 0000000000ffff00 x22: dfff800000000000 x21: 000000000000ffff

x20: ffff0000d432bce0 x19: 000000000000ffff x18: 0000000000000000

x17: 0000000000000000 x16: ffff8000081e1de8 x15: 000000000000003d
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100

x11: 0000000000000000 x10: 1fffe0001a86579c x9 : 0000ffffffffffff
x8 : 0000aaaab4efd0d0 x7 : ffff800008750ed4 x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 00000000fffffff2
Call trace:
prctl_get_tid_address+0x124/0x160 kernel/sys.c:2258
__do_sys_prctl kernel/sys.c:2445 [inline]
__se_sys_prctl kernel/sys.c:2298 [inline]
__arm64_sys_prctl+0x270/0xf14 kernel/sys.c:2298
__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: 94196b82 2a1f03e0 f9400288 f8000aa8 (14000003)

---[ end trace 10129da2b87c289d ]---

----------------
Code disassembly (best guess):
0: 94196b82 bl 0x65ae08
4: 2a1f03e0 mov w0, wzr
8: f9400288 ldr x8, [x20]
c: f8000aa8 sttr x8, [x21]
* 10: 14000003 b 0x1c <-- 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.