Hello,
syzbot found the following issue on:
HEAD commit: dcbcab9d7079 Linux 6.1.174
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10c94760580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link:
https://syzkaller.appspot.com/bug?extid=4c4c5a5720d2c11919ec
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/9a737b79badc/disk-dcbcab9d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/173f40718d47/vmlinux-dcbcab9d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/71c539a3d166/bzImage-dcbcab9d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4c4c5a...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 13789 at net/netfilter/nft_socket.c:220 nft_socket_init+0x2e0/0x3c0 net/netfilter/nft_socket.c:220
Modules linked in:
CPU: 1 PID: 13789 Comm: syz.7.2028 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:nft_socket_init+0x2e0/0x3c0 net/netfilter/nft_socket.c:220
Code: 30 84 c0 0f 85 d8 00 00 00 41 88 2c 24 bd 08 00 00 00 e9 0b ff ff ff 89 f3 e8 0c d8 f8 f8 89 d8 e9 5c ff ff ff e8 00 d8 f8 f8 <0f> 0b e9 4b ff ff ff 89 e9 80 e1 07 38 c1 0f 8c 98 fd ff ff 48 89
RSP: 0018:ffffc900052c7238 EFLAGS: 00010287
RAX: ffffffff8889aeb0 RBX: ffff8880396b0020 RCX: 0000000000080000
RDX: ffffc900168a8000 RSI: 000000000000190b RDI: 000000000000190c
RBP: 00000000000000ff R08: ffffffff8e1ffbef R09: 1ffffffff1c3ff7d
R10: dffffc0000000000 R11: fffffbfff1c3ff7e R12: 0000000000000100
R13: ffff88807beba898 R14: dffffc0000000000 R15: 1ffff110072d6004
FS: 00007f690f03a6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3b7650 CR3: 0000000058cb8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000001800
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nf_tables_newexpr net/netfilter/nf_tables_api.c:3065 [inline]
nf_tables_newrule+0x1731/0x2810 net/netfilter/nf_tables_api.c:3792
nfnetlink_rcv_batch net/netfilter/nfnetlink.c:519 [inline]
nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:639 [inline]
nfnetlink_rcv+0x1124/0x2480 net/netfilter/nfnetlink.c:657
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x74d/0x8d0 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x8ad/0xbd0 net/netlink/af_netlink.c:1872
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5be/0x970 net/socket.c:2518
___sys_sendmsg+0x2a2/0x360 net/socket.c:2572
__sys_sendmsg net/socket.c:2601 [inline]
__do_sys_sendmsg net/socket.c:2610 [inline]
__se_sys_sendmsg+0x1bb/0x2a0 net/socket.c:2608
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f690e19ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f690f03a028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f690e415fa0 RCX: 00007f690e19ce59
RDX: 0000000000000000 RSI: 00002000000002c0 RDI: 0000000000000003
RBP: 00007f690e232d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f690e416038 R14: 00007f690e415fa0 R15: 00007ffd3af94dc8
</TASK>
---
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