[v5.15] BUG: unable to handle kernel paging request in ip6_output

0 views
Skip to first unread message

syzbot

unread,
May 23, 2024, 1:34:38 PMMay 23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 83655231580b Linux 5.15.159
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11277244980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c49fc0ce9b46e64b
dashboard link: https://syzkaller.appspot.com/bug?extid=55c7d55dbeb18611866e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/faa8b26e9d92/disk-83655231.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dacb199b57cf/vmlinux-83655231.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d7c5b8943497/Image-83655231.gz.xz

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

Unable to handle kernel paging request at virtual address dfff8000000000cd
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
[dfff8000000000cd] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 8098 Comm: syz-executor.3 Not tainted 5.15.159-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ip6_output+0x1d4/0x594 net/ipv6/ip6_output.c:224
lr : skb_dst include/linux/skbuff.h:1020 [inline]
lr : ip6_output+0x11c/0x594 net/ipv6/ip6_output.c:219
sp : ffff80001d476e30
x29: ffff80001d476e40 x28: 1fffe00019187fc3 x27: dfff800000000000
x26: 0000000000000000 x25: ffff0000c8c3fdd0 x24: 0000000000000668
x23: 0000000000000000 x22: ffff0000cf6a0000 x21: ffff0000d2e44140
x20: 1fffe00019187fba x19: ffff0000c8c3fdc0 x18: 0000000000000401
x17: 0000000000000002 x16: ffff8000084c430c x15: 0000000000000003
x14: ffff0000d2ee0000 x13: 0000000000ff0100 x12: 0000000000040000
x11: 000000000000a570 x10: ffff80001e5eb000 x9 : 000000000000a571
x8 : 00000000000000cd x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000804685c
x2 : ffff0000c8c3fdc0 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
ip6_output+0x1d4/0x594 net/ipv6/ip6_output.c:224
dst_output include/net/dst.h:443 [inline]
ip6_local_out+0x120/0x160 net/ipv6/output_core.c:161
ip6_send_skb+0x118/0x428 net/ipv6/ip6_output.c:1943
ip6_push_pending_frames+0xd0/0x118 net/ipv6/ip6_output.c:1963
icmpv6_push_pending_frames+0x244/0x398 net/ipv6/icmp.c:311
icmp6_send+0x11a4/0x1b18 net/ipv6/icmp.c:630
__icmpv6_send include/linux/icmpv6.h:28 [inline]
icmpv6_send include/linux/icmpv6.h:49 [inline]
ip6_link_failure+0x44/0x4a8 net/ipv6/route.c:2790
dst_link_failure include/net/dst.h:422 [inline]
xfrmi_xmit2 net/xfrm/xfrm_interface_core.c:383 [inline]
xfrmi_xmit+0x850/0x143c net/xfrm/xfrm_interface_core.c:436
__netdev_start_xmit include/linux/netdevice.h:5019 [inline]
netdev_start_xmit include/linux/netdevice.h:5033 [inline]
xmit_one net/core/dev.c:3617 [inline]
dev_hard_start_xmit+0x2bc/0x92c net/core/dev.c:3633
__dev_queue_xmit+0x13a8/0x2a6c net/core/dev.c:4248
dev_queue_xmit+0x24/0x34 net/core/dev.c:4281
packet_snd net/packet/af_packet.c:3039 [inline]
packet_sendmsg+0x3654/0x4c68 net/packet/af_packet.c:3070
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
__sys_sendto+0x388/0x4d0 net/socket.c:2058
__do_sys_sendto net/socket.c:2070 [inline]
__se_sys_sendto net/socket.c:2066 [inline]
__arm64_sys_sendto+0xd8/0xf8 net/socket.c:2066
__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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9600b877 9119a358 f9000336 d343ff08 (38fb6908)
---[ end trace 8ff622da53742d67 ]---
----------------
Code disassembly (best guess):
0: 9600b877 bl 0xfffffffff802e1dc
4: 9119a358 add x24, x26, #0x668
8: f9000336 str x22, [x25]
c: d343ff08 lsr x8, x24, #3
* 10: 38fb6908 ldrsb w8, [x8, x27] <-- 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
Reply all
Reply to author
Forward
0 new messages