From: syzbot <syzbot+9b35e9bc0951140d13e6@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
horms@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] kernel BUG in ip6_pol_route (2)
Date: Sat, 15 Nov 2025 10:59:20 -0800 [thread overview]
Message-ID: <6918cd88.050a0220.1c914e.0045.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7a0892d2836e Merge tag 'pci-v6.18-fixes-5' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b9a658580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=9b35e9bc0951140d13e6
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/168b5b7f897a/disk-7a0892d2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5d6e756ca306/vmlinux-7a0892d2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d497b0a7a1f5/bzImage-7a0892d2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9b35e9bc0951140d13e6@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/ipv6/route.c:1473!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 9293 Comm: kworker/0:9 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: wg-crypt-wg0 wg_packet_tx_worker
RIP: 0010:rt6_make_pcpu_route net/ipv6/route.c:1473 [inline]
RIP: 0010:ip6_pol_route+0x117d/0x1180 net/ipv6/route.c:2305
Code: ab f8 e9 f4 fa ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 03 fb ff ff 48 89 df e8 ae 04 ab f8 e9 f6 fa ff ff e8 b4 44 49 f8 90 <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e
RSP: 0018:ffffc90004a073c0 EFLAGS: 00010293
RAX: ffffffff8975687c RBX: ffff888126df7000 RCX: ffff888024dd1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90004a074d0 R08: ffffe8ffffc4cdd7 R09: 1ffffd1ffff899ba
R10: dffffc0000000000 R11: fffff91ffff899bb R12: ffff88823bf78f00
R13: ffffffff89755862 R14: dffffc0000000000 R15: 0000607ed8e55dd0
FS: 0000000000000000(0000) GS:ffff888126df7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdadd5ac18 CR3: 00000000370c4000 CR4: 00000000003526f0
Call Trace:
<TASK>
pol_lookup_func include/net/ip6_fib.h:617 [inline]
fib6_rule_lookup+0x1fc/0x6f0 net/ipv6/fib6_rules.c:120
ip6_route_output_flags_noref net/ipv6/route.c:2684 [inline]
ip6_route_output_flags+0x364/0x5d0 net/ipv6/route.c:2696
ip6_dst_lookup_tail+0x299/0x1510 net/ipv6/ip6_output.c:1169
ip6_dst_lookup_flow+0x47/0xe0 net/ipv6/ip6_output.c:1272
send6+0x4ce/0x8d0 drivers/net/wireguard/socket.c:139
wg_socket_send_skb_to_peer+0x128/0x200 drivers/net/wireguard/socket.c:178
wg_packet_create_data_done drivers/net/wireguard/send.c:251 [inline]
wg_packet_tx_worker+0x1c8/0x7c0 drivers/net/wireguard/send.c:276
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:rt6_make_pcpu_route net/ipv6/route.c:1473 [inline]
RIP: 0010:ip6_pol_route+0x117d/0x1180 net/ipv6/route.c:2305
Code: ab f8 e9 f4 fa ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 03 fb ff ff 48 89 df e8 ae 04 ab f8 e9 f6 fa ff ff e8 b4 44 49 f8 90 <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e
RSP: 0018:ffffc90004a073c0 EFLAGS: 00010293
RAX: ffffffff8975687c RBX: ffff888126df7000 RCX: ffff888024dd1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90004a074d0 R08: ffffe8ffffc4cdd7 R09: 1ffffd1ffff899ba
R10: dffffc0000000000 R11: fffff91ffff899bb R12: ffff88823bf78f00
R13: ffffffff89755862 R14: dffffc0000000000 R15: 0000607ed8e55dd0
FS: 0000000000000000(0000) GS:ffff888126df7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdadd5ac18 CR3: 00000000370c4000 CR4: 00000000003526f0
---
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 syzkaller@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
next reply other threads:[~2025-11-15 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 18:59 syzbot [this message]
2025-12-01 2:32 ` [syzbot] [net?] kernel BUG in ip6_pol_route (2) syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6918cd88.050a0220.1c914e.0045.GAE@google.com \
--to=syzbot+9b35e9bc0951140d13e6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox