Message-ID: <6772c485.050a0220.2f3838.04c6.GAE@google.com>
Date: Mon, 30 Dec 2024 08:04:21 -0800
From: syzbot <syzbot+8400677f3fd43f37d3bc@...kaller.appspotmail.com>
To: davem@...emloft.net, edumazet@...gle.com, horms@...nel.org, 
	kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, 
	pabeni@...hat.com, syzkaller-bugs@...glegroups.com, 
	willemdebruijn.kernel@...il.com
Subject: [syzbot] [net?] kernel BUG in vlan_get_tci

Hello,

syzbot found the following issue on:

HEAD commit:    9268abe611b0 Merge branch 'net-lan969x-add-rgmii-support'
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15adaac4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b087c24b921cdc16
dashboard link: https://syzkaller.appspot.com/bug?extid=8400677f3fd43f37d3bc
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=12e1a6df980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13adaac4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8274f60b0163/disk-9268abe6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f7b3fde537e7/vmlinux-9268abe6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/db4cccf7caae/bzImage-9268abe6.xz

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

skbuff: skb_under_panic: text:ffffffff8a8da482 len:4 put:14 head:ffff88804ff34f00 data:ffff88804ff34f10 tail:0x14 end:0x140 dev:<NULL>
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:206!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 5839 Comm: syz-executor403 Not tainted 6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]
RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216
Code: 0b 8d 48 c7 c6 9e 6c 26 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 3a 5a 79 f7 48 83 c4 20 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc900039275b8 EFLAGS: 00010286
RAX: 0000000000000086 RBX: dffffc0000000000 RCX: 562c0de467bbe000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff8880283eca10 R08: ffffffff817f0a4c R09: 1ffff92000724e50
R10: dffffc0000000000 R11: fffff52000724e51 R12: 0000000000000140
R13: ffff88804ff34f00 R14: ffff88804ff34f10 R15: 0000000000000014
FS:  00007f67013ab6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f670138ad58 CR3: 0000000011ed0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 skb_push+0xe5/0x100 net/core/skbuff.c:2636
 vlan_get_tci+0x272/0x550 net/packet/af_packet.c:565
 packet_recvmsg+0x13c9/0x1ef0 net/packet/af_packet.c:3616
 sock_recvmsg_nosec net/socket.c:1044 [inline]
 sock_recvmsg+0x22f/0x280 net/socket.c:1066
 ____sys_recvmsg+0x1c6/0x480 net/socket.c:2814
 ___sys_recvmsg net/socket.c:2856 [inline]
 do_recvmmsg+0x426/0xab0 net/socket.c:2951
 __sys_recvmmsg net/socket.c:3025 [inline]
 __do_sys_recvmmsg net/socket.c:3048 [inline]
 __se_sys_recvmmsg net/socket.c:3041 [inline]
 __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3041
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f67013f05a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f67013ab238 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 00007f670147a348 RCX: 00007f67013f05a9
RDX: 0000000000000001 RSI: 0000000020000480 RDI: 0000000000000003
RBP: 00007f670147a340 R08: 0000000000000000 R09: 00007f67013ab6c0
R10: 0000000000010022 R11: 0000000000000246 R12: 00007f6701447074
R13: 0000000000000000 R14: 00007ffea4c13700 R15: 00007ffea4c137e8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]
RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216
Code: 0b 8d 48 c7 c6 9e 6c 26 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 3a 5a 79 f7 48 83 c4 20 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc900039275b8 EFLAGS: 00010286
RAX: 0000000000000086 RBX: dffffc0000000000 RCX: 562c0de467bbe000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff8880283eca10 R08: ffffffff817f0a4c R09: 1ffff92000724e50
R10: dffffc0000000000 R11: fffff52000724e51 R12: 0000000000000140
R13: ffff88804ff34f00 R14: ffff88804ff34f10 R15: 0000000000000014
FS:  00007f67013ab6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f670138ad58 CR3: 0000000011ed0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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@...glegroups.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

Powered by blists - more mailing lists