[syzbot] [net?] KASAN: global-out-of-bounds Read in macvlan_hard_header (4)

Hello,

syzbot found the following issue on:

HEAD commit:    27e462c8fad4 Merge tag 'xtensa-20230523' of https://github..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10961ec5280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=927d4df6d674370e
dashboard link: https://syzkaller.appspot.com/bug?extid=ae8588da4b5f2e5531d2
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8cc4e9023e9b/disk-27e462c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0fae37d588a6/vmlinux-27e462c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d99575c59a4d/bzImage-27e462c8.xz

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

IPv6: ADDRCONF(NETDEV_CHANGE): team1: link becomes ready
==================================================================
BUG: KASAN: global-out-of-bounds in dev_hard_header include/linux/netdevice.h:3134 [inline]
BUG: KASAN: global-out-of-bounds in macvlan_hard_header+0x12f/0x160 drivers/net/macvlan.c:603
Read of size 8 at addr ffffffff90154998 by task kworker/1:0/21074

CPU: 1 PID: 21074 Comm: kworker/1:0 Not tainted 6.4.0-rc3-syzkaller-00015-g27e462c8fad4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: mld mld_ifc_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:351
 print_report mm/kasan/report.c:462 [inline]
 kasan_report+0x11c/0x130 mm/kasan/report.c:572
 dev_hard_header include/linux/netdevice.h:3134 [inline]
 macvlan_hard_header+0x12f/0x160 drivers/net/macvlan.c:603
 dev_hard_header include/linux/netdevice.h:3137 [inline]
 neigh_resolve_output net/core/neighbour.c:1547 [inline]
 neigh_resolve_output+0x4b7/0x870 net/core/neighbour.c:1532
 neigh_output include/net/neighbour.h:544 [inline]
 ip6_finish_output2+0x55a/0x1560 net/ipv6/ip6_output.c:134
 __ip6_finish_output net/ipv6/ip6_output.c:195 [inline]
 ip6_finish_output+0x69a/0x1170 net/ipv6/ip6_output.c:206
 NF_HOOK_COND include/linux/netfilter.h:292 [inline]
 ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227
 dst_output include/net/dst.h:458 [inline]
 NF_HOOK include/linux/netfilter.h:303 [inline]
 NF_HOOK include/linux/netfilter.h:297 [inline]
 mld_sendpack+0xa09/0xed0 net/ipv6/mcast.c:1820
 mld_send_cr net/ipv6/mcast.c:2121 [inline]
 mld_ifc_work+0x73c/0xe20 net/ipv6/mcast.c:2653
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

The buggy address belongs to the variable:
 nr_zapped_lock_chains+0x18/0x40

The buggy address belongs to the physical page:
page:ffffea0000405500 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10154
flags: 0xfff00000001000(reserved|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000001000 ffffea0000405508 ffffea0000405508 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:
 ffffffff90154880: 00 00 00 00 f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9
 ffffffff90154900: 04 f9 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9

ffffffff90154980: 00 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00 00 00

                            ^
 ffffffff90154a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffffff90154a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup