Hello,
syzbot found the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=176abc1a580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link:
https://syzkaller.appspot.com/bug?extid=1b33c093b885ba7c41ea
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+1b33c0...@syzkaller.appspotmail.com
device syzkaller0 entered promiscuous mode
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7623 at include/linux/skbuff.h:2844 skb_transport_header include/linux/skbuff.h:2844 [inline]
WARNING: CPU: 1 PID: 7623 at include/linux/skbuff.h:2844 tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
WARNING: CPU: 1 PID: 7623 at include/linux/skbuff.h:2844 em_nbyte_match+0x294/0x350 net/sched/em_nbyte.c:43
Modules linked in:
CPU: 1 PID: 7623 Comm: syz.2.1154 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : skb_transport_header include/linux/skbuff.h:2844 [inline]
pc : tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
pc : em_nbyte_match+0x294/0x350 net/sched/em_nbyte.c:43
lr : skb_transport_header include/linux/skbuff.h:2844 [inline]
lr : tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
lr : em_nbyte_match+0x294/0x350 net/sched/em_nbyte.c:43
sp : ffff800021307000
x29: ffff800021307000 x28: 0000000000000001 x27: 000000000000ffff
x26: 1fffe0001ba0223e x25: 1fffe000194769c0 x24: dfff800000000000
x23: 000000000000ffff x22: ffff0000dd0111f6 x21: ffff0000ca3b4e02
x20: ffff0000dd011140 x19: ffff0000ca3b4e00 x18: 0000000000000000
x17: ffff8000181f9000 x16: ffff8000082e7914 x15: 0000000000000002
x14: 0000000000000002 x13: 0000000000ff0100 x12: 0000000000080000
x11: 0000000000000666 x10: ffff80002785a000 x9 : ffff80001002fc2c
x8 : 0000000000000667 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020
x2 : 0000000000000000 x1 : 000000000000ffff x0 : 000000000000ffff
Call trace:
skb_transport_header include/linux/skbuff.h:2844 [inline]
tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
em_nbyte_match+0x294/0x350 net/sched/em_nbyte.c:43
tcf_em_match net/sched/ematch.c:494 [inline]
__tcf_em_tree_match+0x164/0x5bc net/sched/ematch.c:520
tcf_em_tree_match include/net/pkt_cls.h:502 [inline]
basic_classify+0x138/0x30c net/sched/cls_basic.c:48
__tcf_classify net/sched/cls_api.c:1569 [inline]
tcf_classify+0x1b8/0x9c8 net/sched/cls_api.c:1635
multiq_classify net/sched/sch_multiq.c:39 [inline]
multiq_enqueue+0x100/0x404 net/sched/sch_multiq.c:66
dev_qdisc_enqueue+0x5c/0x38c net/core/dev.c:3875
__dev_xmit_skb net/core/dev.c:3964 [inline]
__dev_queue_xmit+0xad0/0x309c net/core/dev.c:4312
dev_queue_xmit+0x24/0x34 include/linux/netdevice.h:3051
packet_snd net/packet/af_packet.c:3127 [inline]
packet_sendmsg+0x2f6c/0x3fac net/packet/af_packet.c:3158
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5b8/0x918 net/socket.c:2519
___sys_sendmsg net/socket.c:2573 [inline]
__sys_sendmsg+0x25c/0x320 net/socket.c:2602
__do_sys_sendmsg net/socket.c:2611 [inline]
__se_sys_sendmsg net/socket.c:2609 [inline]
__arm64_sys_sendmsg+0x80/0x94 net/socket.c:2609
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 3199
hardirqs last enabled at (3197): [<ffff800008059424>] local_daif_restore arch/arm64/include/asm/daifflags.h:75 [inline]
hardirqs last enabled at (3197): [<ffff800008059424>] el0_svc_common+0x9c/0x258 arch/arm64/kernel/syscall.c:105
hardirqs last disabled at (3199): [<ffff80001195cc30>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (3192): [<ffff8000080309e0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (3198): [<ffff80000fd41b10>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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