[syzbot] [ext4?] [net?] general protection fault in __dev_set_rx_mode

[syzbot <syzbot+b0e409c0b9976e4b3923@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    92514ef226f5 Merge tag 'for-6.14-rc1-tag' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=162e5318580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1909f2f0d8e641ce
dashboard link: https://syzkaller.appspot.com/bug?extid=b0e409c0b9976e4b3923
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=149d41b0580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-92514ef2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c4d8b91f8769/vmlinux-92514ef2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c24ec4365966/bzImage-92514ef2.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2fed19de440d/mount_0.gz

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

Oops: general protection fault, probably for non-canonical address 0xffec282c2c2c2c34: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0xff616161616161a0-0xff616161616161a7]
CPU: 0 UID: 0 PID: 30 Comm: kworker/u4:2 Not tainted 6.14.0-rc1-syzkaller-00034-g92514ef226f5 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: ipv6_addrconf addrconf_dad_work
RIP: 0010:__dev_set_rx_mode+0x1c2/0x280 net/core/dev.c:9092
Code: 8b 04 24 42 0f b6 04 20 84 c0 48 8b 5c 24 08 0f 85 b3 00 00 00 40 88 2b eb 05 e8 e9 78 00 f8 49 83 c6 40 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 3f 11 67 f8 49 8b 2e 48 85 ed 74
RSP: 0018:ffffc900005177e0 EFLAGS: 00010a02
RAX: 1fec2c2c2c2c2c34 RBX: ffff888042c70410 RCX: ffff888030eca440
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff89bee4d6 R09: 1ffff1100858e015
R10: dffffc0000000000 R11: ffffed100858e016 R12: dffffc0000000000
R13: ffff888042c70000 R14: ff616161616161a1 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4808733114 CR3: 000000003efa4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __dev_mc_add net/core/dev_addr_lists.c:872 [inline]
 dev_mc_add+0xca/0x110 net/core/dev_addr_lists.c:886
 igmp6_group_added+0x1a4/0x710 net/ipv6/mcast.c:684
 __ipv6_dev_mc_inc+0x8da/0xac0 net/ipv6/mcast.c:988
 addrconf_join_solict net/ipv6/addrconf.c:2240 [inline]
 addrconf_dad_begin net/ipv6/addrconf.c:4095 [inline]
 addrconf_dad_work+0x44f/0x16a0 net/ipv6/addrconf.c:4223
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317
 worker_thread+0x870/0xd30 kernel/workqueue.c:3398
 kthread+0x7a9/0x920 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__dev_set_rx_mode+0x1c2/0x280 net/core/dev.c:9092
Code: 8b 04 24 42 0f b6 04 20 84 c0 48 8b 5c 24 08 0f 85 b3 00 00 00 40 88 2b eb 05 e8 e9 78 00 f8 49 83 c6 40 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 3f 11 67 f8 49 8b 2e 48 85 ed 74
RSP: 0018:ffffc900005177e0 EFLAGS: 00010a02
RAX: 1fec2c2c2c2c2c34 RBX: ffff888042c70410 RCX: ffff888030eca440
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff89bee4d6 R09: 1ffff1100858e015
R10: dffffc0000000000 R11: ffffed100858e016 R12: dffffc0000000000
R13: ffff888042c70000 R14: ff616161616161a1 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4808733114 CR3: 000000003efa4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	8b 04 24             	mov    (%rsp),%eax
   3:	42 0f b6 04 20       	movzbl (%rax,%r12,1),%eax
   8:	84 c0                	test   %al,%al
   a:	48 8b 5c 24 08       	mov    0x8(%rsp),%rbx
   f:	0f 85 b3 00 00 00    	jne    0xc8
  15:	40 88 2b             	mov    %bpl,(%rbx)
  18:	eb 05                	jmp    0x1f
  1a:	e8 e9 78 00 f8       	call   0xf8007908
  1f:	49 83 c6 40          	add    $0x40,%r14
  23:	4c 89 f0             	mov    %r14,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 80 3c 20 00       	cmpb   $0x0,(%rax,%r12,1) <-- trapping instruction
  2f:	74 08                	je     0x39
  31:	4c 89 f7             	mov    %r14,%rdi
  34:	e8 3f 11 67 f8       	call   0xf8671178
  39:	49 8b 2e             	mov    (%r14),%rbp
  3c:	48 85 ed             	test   %rbp,%rbp
  3f:	74                   	.byte 0x74


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