[v6.1] BUG: unable to handle kernel paging request in rose_transmit_link

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8ce36b2849ef Linux 6.1.163
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1230895a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=55358196b0552f16868f
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.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/e71ac74ccc11/disk-8ce36b28.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a090f33b3222/vmlinux-8ce36b28.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13fb3beccc73/Image-8ce36b28.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000006
KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000006] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4435 Comm: syz.3.4 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : rose_transmit_link+0x40/0x668 net/rose/rose_link.c:266
lr : rose_transmit_link+0x34/0x668 net/rose/rose_link.c:263
sp : ffff800021327760
x29: ffff800021327760 x28: dfff800000000000 x27: ffff700004264efc
x26: dfff800000000000 x25: 0000000000000032 x24: 0000000000000000
x23: ffff0000c46595ad x22: 0000000000000000 x21: 0000000000000036
x20: ffff0000d1d15b40 x19: 0000000000000000 x18: ffff800011b8bf60
x17: ffff80000fd47170 x16: ffff8000082d9364 x15: 0000000000000002
x14: 000000000000000f x13: 0000000000ff0100 x12: 0000000000080000
x11: 00000000000066f6 x10: ffff800025f19000 x9 : 0000000000000006
x8 : 0000000000000006 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : 0000000000000000 x3 : ffff80000fd637bc
x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff0000d1d15b40
Call trace:
rose_transmit_link+0x40/0x668 net/rose/rose_link.c:266
rose_write_internal+0xefc/0x17d0 net/rose/rose_subr.c:198
rose_release+0x208/0x4d4 net/rose/af_rose.c:671
__sock_release net/socket.c:654 [inline]
sock_close+0xb4/0x1f8 net/socket.c:1399
__fput+0x1bc/0x7b8 fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x1ec/0x278 kernel/task_work.c:203
get_signal+0x111c/0x1304 kernel/signal.c:2648
do_signal arch/arm64/kernel/signal.c:1095 [inline]
do_notify_resume+0x33c/0x2aa4 arch/arm64/kernel/signal.c:1148
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x98/0x128 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 97d1b2a8 9100da75 d343fea8 12000aa9 (38fa6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 97d1b2a8 bl 0xffffffffff46caa0
4: 9100da75 add x21, x19, #0x36
8: d343fea8 lsr x8, x21, #3
c: 12000aa9 and w9, w21, #0x7
* 10: 38fa6908 ldrsb w8, [x8, x26] <-- 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: 8ce36b2849ef Linux 6.1.163
git tree: linux-6.1.y

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

kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=55358196b0552f16868f
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15349ee6580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=143f6ffa580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e71ac74ccc11/disk-8ce36b28.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a090f33b3222/vmlinux-8ce36b28.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13fb3beccc73/Image-8ce36b28.gz.xz

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

IPv6: ADDRCONF(NETDEV_CHANGE): bpq0: link becomes ready

Unable to handle kernel paging request at virtual address dfff800000000006
KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000006] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4455 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : rose_transmit_link+0x40/0x668 net/rose/rose_link.c:266
lr : rose_transmit_link+0x34/0x668 net/rose/rose_link.c:263

sp : ffff800021567760
x29: ffff800021567760 x28: dfff800000000000 x27: ffff7000042acefc

x26: dfff800000000000 x25: 0000000000000032 x24: 0000000000000000

x23: ffff0000d4aec5ad x22: 0000000000000000 x21: 0000000000000036
x20: ffff0000d14d1280 x19: 0000000000000000 x18: ffff800011b8bf60
x17: ffff80000fd47170 x16: ffff8000082d9364 x15: 0000000000000000
x14: 000000000000000f x13: 0000000000ff0100 x12: 0000000000ff0100
x11: ff00800010b80a94 x10: 0000000000000000 x9 : 0000000000000006

x8 : 0000000000000006 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : 0000000000000000 x3 : ffff80000fd637bc

x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff0000d14d1280

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.