[v5.15] KASAN: use-after-free Read in team_xmit

1 view
Skip to first unread message

syzbot

unread,
Jun 17, 2026, 12:06:36 AM (4 days ago) Jun 17
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: dc027a595035 Linux 5.15.209
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c214ae580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=8fbaab7e22f00570bdd2
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/586ac2a2fd9d/disk-dc027a59.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/06dcb6a2fcd3/vmlinux-dc027a59.xz
kernel image: https://storage.googleapis.com/syzbot-assets/567131e0cbcc/bzImage-dc027a59.xz

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

==================================================================
BUG: KASAN: use-after-free in team_dev_queue_xmit include/linux/if_team.h:235 [inline]
BUG: KASAN: use-after-free in team_queue_override_transmit drivers/net/team/team.c:810 [inline]
BUG: KASAN: use-after-free in team_xmit+0x266/0x4d0 drivers/net/team/team.c:1740
Read of size 2 at addr ffff888046db266c by task syz.2.8161/30679

CPU: 1 PID: 30679 Comm: syz.2.8161 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
print_address_description+0x60/0x2d0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xdf/0x130 mm/kasan/report.c:451
team_dev_queue_xmit include/linux/if_team.h:235 [inline]
team_queue_override_transmit drivers/net/team/team.c:810 [inline]
team_xmit+0x266/0x4d0 drivers/net/team/team.c:1740
__netdev_start_xmit include/linux/netdevice.h:5036 [inline]
netdev_start_xmit include/linux/netdevice.h:5050 [inline]
__dev_direct_xmit+0x4b6/0x720 net/core/dev.c:4382
dev_direct_xmit include/linux/netdevice.h:3018 [inline]
packet_direct_xmit+0x164/0x2b0 net/packet/af_packet.c:246
packet_snd net/packet/af_packet.c:3089 [inline]
packet_sendmsg+0x3dba/0x5060 net/packet/af_packet.c:3120
sock_sendmsg_nosec net/socket.c:706 [inline]
__sock_sendmsg net/socket.c:718 [inline]
____sys_sendmsg+0x5b7/0x8f0 net/socket.c:2445
___sys_sendmsg+0x236/0x2e0 net/socket.c:2499
__sys_sendmmsg+0x2ba/0x500 net/socket.c:2585
__do_sys_sendmmsg net/socket.c:2614 [inline]
__se_sys_sendmmsg net/socket.c:2611 [inline]
__x64_sys_sendmmsg+0x9c/0xb0 net/socket.c:2611
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f86b9cf9e59
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:00007f86b7f53028 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007f86b9f72fa0 RCX: 00007f86b9cf9e59
RDX: 0000000000000001 RSI: 0000200000000440 RDI: 000000000000000e
RBP: 00007f86b9d8fd6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f86b9f73038 R14: 00007f86b9f72fa0 R15: 00007ffcde8fe4e8
</TASK>

Allocated by task 30679:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
__kasan_slab_alloc+0x9c/0xd0 mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x4c/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3225 [inline]
kmem_cache_alloc_node+0x12d/0x2d0 mm/slub.c:3261
__alloc_skb+0xf4/0x750 net/core/skbuff.c:415
alloc_skb include/linux/skbuff.h:1162 [inline]
alloc_skb_with_frags+0xa7/0x730 net/core/skbuff.c:6183
sock_alloc_send_pskb+0x87f/0x9a0 net/core/sock.c:2536
packet_alloc_skb net/packet/af_packet.c:2936 [inline]
packet_snd net/packet/af_packet.c:3031 [inline]
packet_sendmsg+0x343c/0x5060 net/packet/af_packet.c:3120
sock_sendmsg_nosec net/socket.c:706 [inline]
__sock_sendmsg net/socket.c:718 [inline]
____sys_sendmsg+0x5b7/0x8f0 net/socket.c:2445
___sys_sendmsg+0x236/0x2e0 net/socket.c:2499
__sys_sendmmsg+0x2ba/0x500 net/socket.c:2585
__do_sys_sendmmsg net/socket.c:2614 [inline]
__se_sys_sendmmsg net/socket.c:2611 [inline]
__x64_sys_sendmmsg+0x9c/0xb0 net/socket.c:2611
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

Freed by task 30679:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kmem_cache_free+0x8f/0x210 mm/slub.c:3520
__kfree_skb net/core/skbuff.c:757 [inline]
kfree_skb_reason net/core/skbuff.c:776 [inline]
kfree_skb include/linux/skbuff.h:1118 [inline]
kfree_skb_list+0xcc/0x140 net/core/skbuff.c:785
__dev_xmit_skb net/core/dev.c:3961 [inline]
__dev_queue_xmit+0x2024/0x2f80 net/core/dev.c:4266
team_dev_queue_xmit include/linux/if_team.h:242 [inline]
team_queue_override_transmit drivers/net/team/team.c:810 [inline]
team_xmit+0x238/0x4d0 drivers/net/team/team.c:1740
__netdev_start_xmit include/linux/netdevice.h:5036 [inline]
netdev_start_xmit include/linux/netdevice.h:5050 [inline]
__dev_direct_xmit+0x4b6/0x720 net/core/dev.c:4382
dev_direct_xmit include/linux/netdevice.h:3018 [inline]
packet_direct_xmit+0x164/0x2b0 net/packet/af_packet.c:246
packet_snd net/packet/af_packet.c:3089 [inline]
packet_sendmsg+0x3dba/0x5060 net/packet/af_packet.c:3120
sock_sendmsg_nosec net/socket.c:706 [inline]
__sock_sendmsg net/socket.c:718 [inline]
____sys_sendmsg+0x5b7/0x8f0 net/socket.c:2445
___sys_sendmsg+0x236/0x2e0 net/socket.c:2499
__sys_sendmmsg+0x2ba/0x500 net/socket.c:2585
__do_sys_sendmmsg net/socket.c:2614 [inline]
__se_sys_sendmmsg net/socket.c:2611 [inline]
__x64_sys_sendmmsg+0x9c/0xb0 net/socket.c:2611
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

The buggy address belongs to the object at ffff888046db2640
which belongs to the cache skbuff_head_cache of size 232
The buggy address is located 44 bytes inside of
232-byte region [ffff888046db2640, ffff888046db2728)
The buggy address belongs to the page:
page:ffffea00011b6c80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x46db2
memcg:ffff88802277d601
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 ffffea00018e9180 0000000900000009 ffff88801bbe5140
raw: 0000000000000000 00000000800c000c 00000001ffffffff ffff88802277d601
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x112cc0(GFP_USER|__GFP_NOWARN|__GFP_NORETRY), pid 3853, ts 1762917660770, free_ts 1762917212507
prep_new_page mm/page_alloc.c:2426 [inline]
get_page_from_freelist+0x1bbd/0x1ca0 mm/page_alloc.c:4192
__alloc_pages+0x1ee/0x480 mm/page_alloc.c:5501
alloc_slab_page mm/slub.c:1780 [inline]
allocate_slab mm/slub.c:1917 [inline]
new_slab+0xc0/0x4b0 mm/slub.c:1980
___slab_alloc+0x80a/0xdd0 mm/slub.c:3013
__slab_alloc mm/slub.c:3100 [inline]
slab_alloc_node mm/slub.c:3191 [inline]
kmem_cache_alloc_node+0x1c3/0x2d0 mm/slub.c:3261
__alloc_skb+0xf4/0x750 net/core/skbuff.c:415
alloc_skb include/linux/skbuff.h:1162 [inline]
alloc_skb_with_frags+0xa7/0x730 net/core/skbuff.c:6183
sock_alloc_send_pskb+0x87f/0x9a0 net/core/sock.c:2536
unix_dgram_sendmsg+0x5fc/0x18a0 net/unix/af_unix.c:1809
sock_sendmsg_nosec net/socket.c:706 [inline]
__sock_sendmsg net/socket.c:718 [inline]
__sys_sendto+0x46d/0x620 net/socket.c:2072
__do_sys_sendto net/socket.c:2084 [inline]
__se_sys_sendto net/socket.c:2080 [inline]
__x64_sys_sendto+0xda/0xf0 net/socket.c:2080
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1340 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0x637/0x6c0 mm/page_alloc.c:3317
free_unref_page+0x8f/0x2a0 mm/page_alloc.c:3396
mm_free_pgd kernel/fork.c:653 [inline]
__mmdrop+0xaa/0x3e0 kernel/fork.c:704
mmdrop include/linux/sched/mm.h:49 [inline]
finish_task_switch+0x215/0x640 kernel/sched/core.c:4948
context_switch kernel/sched/core.c:5052 [inline]
__schedule+0x11f7/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_hrtimeout_range_clock+0x239/0x590 kernel/time/hrtimer.c:2277
poll_schedule_timeout+0x10b/0x150 fs/select.c:243
do_poll fs/select.c:964 [inline]
do_sys_poll+0x7d1/0x11a0 fs/select.c:1014
__do_sys_ppoll fs/select.c:1120 [inline]
__se_sys_ppoll+0x206/0x2a0 fs/select.c:1100
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

Memory state around the buggy address:
ffff888046db2500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888046db2580: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc
>ffff888046db2600: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb
^
ffff888046db2680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888046db2700: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc
==================================================================


---
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
Reply all
Reply to author
Forward
0 new messages