Hello,
syzbot found the following issue on:
HEAD commit: cd9b81672742 Linux 6.1.161
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1168bf9a580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link:
https://syzkaller.appspot.com/bug?extid=7cd568ea0d8c6ada6cbe
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.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/d21df4411014/disk-cd9b8167.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/246aed0358fb/vmlinux-cd9b8167.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a6f546504ec2/Image-cd9b8167.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7cd568...@syzkaller.appspotmail.com
device syzkaller0 entered promiscuous mode
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5126 at include/linux/skbuff.h:2844 skb_transport_header include/linux/skbuff.h:2844 [inline]
WARNING: CPU: 1 PID: 5126 at include/linux/skbuff.h:2844 tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
WARNING: CPU: 1 PID: 5126 at include/linux/skbuff.h:2844 em_cmp_match+0x40c/0x5c0 net/sched/em_cmp.c:25
Modules linked in:
CPU: 1 PID: 5126 Comm: syz.0.235 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_cmp_match+0x40c/0x5c0 net/sched/em_cmp.c:25
lr : skb_transport_header include/linux/skbuff.h:2844 [inline]
lr : tcf_get_base_ptr include/net/pkt_cls.h:529 [inline]
lr : em_cmp_match+0x40c/0x5c0 net/sched/em_cmp.c:25
sp : ffff8000210c6fc0
x29: ffff8000210c6fc0 x28: 0000000000000001 x27: 000000000000ffff
x26: 1fffe0001b0fcfa6 x25: 1fffe0001e5d5f61 x24: dfff800000000000
x23: 000000000000ffff x22: ffff0000d87e7d36 x21: ffff0000f2eafb0a
x20: ffff0000d87e7c80 x19: ffff0000f2eafb00 x18: 0000000000000000
x17: ffff800018338000 x16: ffff8000082eeb30 x15: 0000000000000002
x14: 0000000000000002 x13: 0000000000ff0100 x12: 0000000000080000
x11: 00000000000008b4 x10: ffff800021c4c000 x9 : ffff8000100b822c
x8 : 00000000000008b5 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_cmp_match+0x40c/0x5c0 net/sched/em_cmp.c:25
tcf_em_match net/sched/ematch.c:494 [inline]
__tcf_em_tree_match+0x180/0x5e4 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/0x9c4 net/sched/cls_api.c:1635
htb_classify net/sched/sch_htb.c:242 [inline]
htb_enqueue+0x2fc/0xf04 net/sched/sch_htb.c:622
dev_qdisc_enqueue+0x5c/0x388 net/core/dev.c:3875
__dev_xmit_skb net/core/dev.c:3964 [inline]
__dev_queue_xmit+0xaf8/0x3134 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+0x2f9c/0x3fd0 net/packet/af_packet.c:3158
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5c8/0x938 net/socket.c:2518
___sys_sendmsg net/socket.c:2572 [inline]
__sys_sendmsg+0x288/0x374 net/socket.c:2601
__do_sys_sendmsg net/socket.c:2610 [inline]
__se_sys_sendmsg net/socket.c:2608 [inline]
__arm64_sys_sendmsg+0x80/0x94 net/socket.c:2608
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 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: 2925
hardirqs last enabled at (2923): [<ffff800011b072cc>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (2923): [<ffff800011b072cc>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (2925): [<ffff800011a1c234>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (2908): [<ffff800008030954>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (2924): [<ffff80000fdc3444>] 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