================================================================== BUG: KASAN: global-out-of-bounds in fib6_clean_node+0x35d/0x590 net/ipv6/ip6_fib.c:2198 Read of size 8 at addr ffffffff99ce15e8 by task syz-executor/7340 CPU: 0 UID: 0 PID: 7340 Comm: syz-executor Not tainted 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xb4/0x290 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 fib6_clean_node+0x35d/0x590 net/ipv6/ip6_fib.c:2198 fib6_walk_continue+0x678/0x910 net/ipv6/ip6_fib.c:2124 fib6_walk+0x149/0x290 net/ipv6/ip6_fib.c:2172 fib6_clean_tree net/ipv6/ip6_fib.c:2252 [inline] __fib6_clean_all+0x234/0x380 net/ipv6/ip6_fib.c:2268 rt6_sync_down_dev net/ipv6/route.c:4951 [inline] rt6_disable_ip+0x120/0x720 net/ipv6/route.c:4956 addrconf_ifdown+0x15d/0x1880 net/ipv6/addrconf.c:3854 addrconf_notify+0x1bc/0x1010 net/ipv6/addrconf.c:-1 notifier_call_chain+0x1b3/0x3e0 kernel/notifier.c:85 call_netdevice_notifiers_extack net/core/dev.c:2214 [inline] call_netdevice_notifiers net/core/dev.c:2228 [inline] dev_close_many+0x29c/0x410 net/core/dev.c:1731 unregister_netdevice_many_notify+0x834/0x2330 net/core/dev.c:11952 unregister_netdevice_many net/core/dev.c:12046 [inline] unregister_netdevice_queue+0x33c/0x380 net/core/dev.c:11889 unregister_netdevice include/linux/netdevice.h:3374 [inline] __tun_detach+0xda4/0x1560 drivers/net/tun.c:620 tun_detach drivers/net/tun.c:636 [inline] tun_chr_close+0x10a/0x1c0 drivers/net/tun.c:3390 __fput+0x449/0xa70 fs/file_table.c:465 task_work_run+0x1d1/0x260 kernel/task_work.c:227 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0x8d6/0x2550 kernel/exit.c:953 do_group_exit+0x21c/0x2d0 kernel/exit.c:1102 __do_sys_exit_group kernel/exit.c:1113 [inline] __se_sys_exit_group kernel/exit.c:1111 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1111 x64_sys_call+0x21ba/0x21c0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f9cd918e969 Code: Unable to access opcode bytes at 0x7f9cd918e93f. RSP: 002b:00007ffc3365f9e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f9cd92108c2 RCX: 00007f9cd918e969 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 RBP: 0000000000000002 R08: 00007ffc3365d787 R09: 00007ffc33660ca0 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc33660ca0 R13: 00007f9cd921089d R14: 00005555919004a8 R15: 00007ffc33661d70 The buggy address belongs to the variable: binder_devices+0x8/0x20 The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x19ce1 flags: 0xfff00000002000(reserved|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000002000 ffffea0000673848 ffffea0000673848 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffffffff99ce1480: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 ffffffff99ce1500: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 >ffffffff99ce1580: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 ^ ffffffff99ce1600: 00 00 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00 ffffffff99ce1680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================