[v5.15] WARNING in br_nf_local_in

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e89efd3ae1c Linux 5.15.164
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0696d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8e7768447c833306
dashboard link: https://syzkaller.appspot.com/bug?extid=6a1ac04cc8777e654f45
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/3d929e236949/disk-7e89efd3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8a76a46947c4/vmlinux-7e89efd3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12f4fa036ad7/Image-7e89efd3.gz.xz

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

bridge0: received packet on syz_tun with own address as source address (addr:aa:aa:aa:aa:aa:aa, vlan:0)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4523 at net/bridge/br_netfilter_hooks.c:629 br_nf_local_in+0x424/0x49c net/bridge/br_netfilter_hooks.c:629
Modules linked in:
CPU: 0 PID: 4523 Comm: syz.0.107 Not tainted 5.15.164-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : br_nf_local_in+0x424/0x49c net/bridge/br_netfilter_hooks.c:629
lr : br_nf_local_in+0x424/0x49c net/bridge/br_netfilter_hooks.c:629
sp : ffff80001d4368d0
x29: ffff80001d4368f0 x28: ffff0000e793e710 x27: 0000000000000010
x26: 0000000000000180 x25: 1fffe00019cc6448 x24: dfff800000000000
x23: ffff8000136672e0 x22: ffff0000ce632240 x21: ffff0000e495fdc0
x20: 0000000000000000 x19: 0000000000000180 x18: 0000000000000402
x17: 0000000000000000 x16: ffff8000084c36cc x15: 0000000000000088
x14: 1ffff0000295806a x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000000200 x10: 0000000000000000 x9 : ffff0000d15e0000
x8 : ffff800010c83844 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80000804605c
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
br_nf_local_in+0x424/0x49c net/bridge/br_netfilter_hooks.c:629
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_slow+0xc8/0x1f4 net/netfilter/core.c:584
nf_hook include/linux/netfilter.h:257 [inline]
NF_HOOK+0x2b0/0x3e0 include/linux/netfilter.h:300
br_pass_frame_up+0x29c/0x3ec net/bridge/br_input.c:70
br_handle_frame_finish+0xe94/0x1264
br_nf_pre_routing_finish+0x1190/0x1a4c net/bridge/br_netfilter_hooks.c:428
NF_HOOK+0x690/0x740 include/linux/netfilter.h:302
br_nf_pre_routing+0xb04/0x102c net/bridge/br_netfilter_hooks.c:537
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_bridge_pre net/bridge/br_input.c:242 [inline]
br_handle_frame+0x86c/0xedc net/bridge/br_input.c:384
__netif_receive_skb_core+0xf10/0x341c net/core/dev.c:5379
__netif_receive_skb_one_core net/core/dev.c:5483 [inline]
__netif_receive_skb+0x114/0x400 net/core/dev.c:5599
netif_receive_skb_internal net/core/dev.c:5685 [inline]
netif_receive_skb+0x1e0/0x8c4 net/core/dev.c:5744
tun_rx_batched+0x568/0x6e4
tun_get_user+0x2320/0x3774 drivers/net/tun.c:1989
tun_chr_write_iter+0xfc/0x20c drivers/net/tun.c:2019
call_write_iter include/linux/fs.h:2172 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x884/0xb44 fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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
irq event stamp: 155
hardirqs last enabled at (154): [<ffff8000081b55fc>] __local_bh_enable_ip+0x230/0x470 kernel/softirq.c:388
hardirqs last disabled at (155): [<ffff800011ab40b4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (46): [<ffff80000c92aa20>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (48): [<ffff80000c92a9ec>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 7a2941048dd4b01c ]---
netlink: 20 bytes leftover after parsing attributes in process `syz.0.107'.


---
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.