All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cb809def1baaac68ab92@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 fib6_add_rt2node (2)
Date: Tue, 06 Jan 2026 09:58:18 -0800	[thread overview]
Message-ID: <695d4d3a.050a0220.1c677c.0349.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    1d528e794f3d Merge branch 'bpf-fix-bpf_d_path-helper-proto..
git tree:       bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=159c51c2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9e5198eaf003f1d1
dashboard link: https://syzkaller.appspot.com/bug?extid=cb809def1baaac68ab92
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=139c51c2580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11b2961a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aec210aa3af6/disk-1d528e79.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7d58dbcc713/vmlinux-1d528e79.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c22e61a8447d/bzImage-1d528e79.xz

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

------------[ cut here ]------------
kernel BUG at net/ipv6/ip6_fib.c:1217!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6010 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:fib6_add_rt2node+0x3433/0x3470 net/ipv6/ip6_fib.c:1217
Code: ff ff 48 8b 4c 24 08 80 e1 07 80 c1 03 38 c1 0f 8c a4 f9 ff ff 48 8b 7c 24 08 e8 08 4d 28 f8 e9 95 f9 ff ff e8 0e 64 c2 f7 90 <0f> 0b 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 7a fa ff ff 4c 89 ff
RSP: 0018:ffffc900030a7660 EFLAGS: 00010293
RAX: ffffffff89fee772 RBX: 0000000000000001 RCX: ffff88807a2abd00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: ffffc900030a7850 R08: ffffc900030a7910 R09: 0000000000000050
R10: 0000000000000000 R11: fffff52000614f24 R12: ffff888074779818
R13: ffff888074779800 R14: dffffc0000000000 R15: 0000000000000002
FS:  000055556dfd5500(0000) GS:ffff8881260b1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000074636000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 fib6_add+0x8da/0x18a0 net/ipv6/ip6_fib.c:1532
 __ip6_ins_rt net/ipv6/route.c:1351 [inline]
 ip6_route_add+0xde/0x1b0 net/ipv6/route.c:3946
 ipv6_route_ioctl+0x35c/0x480 net/ipv6/route.c:4571
 inet6_ioctl+0x219/0x280 net/ipv6/af_inet6.c:577
 sock_do_ioctl+0xdc/0x300 net/socket.c:1245
 sock_ioctl+0x576/0x790 net/socket.c:1366
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbf1918f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe117d8c08 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fbf193e5fa0 RCX: 00007fbf1918f749
RDX: 0000200000000000 RSI: 000000000000890b RDI: 0000000000000007
RBP: 00007fbf19213f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbf193e5fa0 R14: 00007fbf193e5fa0 R15: 0000000000000003
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:fib6_add_rt2node+0x3433/0x3470 net/ipv6/ip6_fib.c:1217
Code: ff ff 48 8b 4c 24 08 80 e1 07 80 c1 03 38 c1 0f 8c a4 f9 ff ff 48 8b 7c 24 08 e8 08 4d 28 f8 e9 95 f9 ff ff e8 0e 64 c2 f7 90 <0f> 0b 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 7a fa ff ff 4c 89 ff
RSP: 0018:ffffc900030a7660 EFLAGS: 00010293
RAX: ffffffff89fee772 RBX: 0000000000000001 RCX: ffff88807a2abd00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000001
RBP: ffffc900030a7850 R08: ffffc900030a7910 R09: 0000000000000050
R10: 0000000000000000 R11: fffff52000614f24 R12: ffff888074779818
R13: ffff888074779800 R14: dffffc0000000000 R15: 0000000000000002
FS:  000055556dfd5500(0000) GS:ffff8881260b1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000074636000 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 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.

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	other threads:[~2026-01-06 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 17:58 syzbot [this message]
2026-01-09  0:56 ` [syzbot] [net?] kernel BUG in fib6_add_rt2node (2) David Ahern
2026-02-04  8:12 ` Forwarded: Test for cb809def1baaac68ab92 syzbot
     [not found] <87wm0tylkf.fsf@redhat.com>
2026-02-04  9:46 ` [syzbot] [net?] kernel BUG in fib6_add_rt2node (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=695d4d3a.050a0220.1c677c.0349.GAE@google.com \
    --to=syzbot+cb809def1baaac68ab92@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.