The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+ecbb1750082f7528b507@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] KASAN: slab-use-after-free Read in vhci_send_cmd_submit
Date: Thu, 20 Aug 2026 07:58:25 -0700	[thread overview]
Message-ID: <6a871611.4d75e56a.c9a88.0041.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    3eb40771c00a Merge tag 'soc-fixes-7.2-3' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e07a79580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1d67342c314f228d
dashboard link: https://syzkaller.appspot.com/bug?extid=ecbb1750082f7528b507
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12849949580000

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

==================================================================
BUG: KASAN: slab-use-after-free in vhci_send_cmd_submit+0xed2/0x10c0 drivers/usb/usbip/vhci_tx.c:91
Read of size 4 at addr ffff888022a66584 by task vhci_tx/6044

CPU: 0 UID: 0 PID: 6044 Comm: vhci_tx Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0x13d/0x4b0 mm/kasan/report.c:482
 kasan_report+0xdf/0x1c0 mm/kasan/report.c:595
 vhci_send_cmd_submit+0xed2/0x10c0 drivers/usb/usbip/vhci_tx.c:91
 vhci_tx_loop+0xff/0x460 drivers/usb/usbip/vhci_tx.c:241
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Allocated by task 6031:
 kasan_save_stack+0x30/0x50 mm/kasan/common.c:57
 kasan_save_track+0x14/0x30 mm/kasan/common.c:78
 poison_kmalloc_redzone mm/kasan/common.c:398 [inline]
 __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:415
 kasan_kmalloc include/linux/kasan.h:263 [inline]
 __do_kmalloc_node mm/slub.c:5334 [inline]
 __kmalloc_noprof+0x322/0x820 mm/slub.c:5359
 _kmalloc_noprof include/linux/slab.h:992 [inline]
 usb_alloc_urb+0x66/0xa0 drivers/usb/core/urb.c:75
 alloc_async drivers/usb/core/devio.c:408 [inline]
 proc_do_submiturb+0x741/0x3820 drivers/usb/core/devio.c:1780
 proc_submiturb drivers/usb/core/devio.c:2002 [inline]
 usbdev_do_ioctl drivers/usb/core/devio.c:2702 [inline]
 usbdev_ioctl+0x2adb/0x3aa0 drivers/usb/core/devio.c:2826
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 6031:
 kasan_save_stack+0x30/0x50 mm/kasan/common.c:57
 kasan_save_track+0x14/0x30 mm/kasan/common.c:78
 kasan_save_free_info+0x3b/0x70 mm/kasan/generic.c:584
 poison_slab_object mm/kasan/common.c:253 [inline]
 __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:285
 kasan_slab_free include/linux/kasan.h:235 [inline]
 slab_free_hook mm/slub.c:2677 [inline]
 slab_free mm/slub.c:6377 [inline]
 kfree+0x22b/0x6c0 mm/slub.c:6692
 urb_destroy drivers/usb/core/urb.c:27 [inline]
 kref_put include/linux/kref.h:65 [inline]
 usb_free_urb.part.0+0xa5/0x110 drivers/usb/core/urb.c:96
 usb_free_urb+0x1f/0x30 drivers/usb/core/urb.c:95
 free_async+0x358/0x530 drivers/usb/core/devio.c:435
 proc_reapurbnonblock drivers/usb/core/devio.c:2129 [inline]
 usbdev_do_ioctl drivers/usb/core/devio.c:2621 [inline]
 usbdev_ioctl+0x2e7/0x3aa0 drivers/usb/core/devio.c:2826
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff888022a66500
 which belongs to the cache kmalloc-192 of size 192
The buggy address is located 132 bytes inside of
 freed 192-byte region [ffff888022a66500, ffff888022a665c0)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x22a66
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 00fff00000000000 ffff88801c0423c0 dead000000000100 dead000000000122
raw: 0000000000000000 0000000800100010 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0xd2cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, tgid 1 (swapper/0), ts 5964583883, free_ts 0
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0xfd/0x120 mm/page_alloc.c:1859
 prep_new_page mm/page_alloc.c:1867 [inline]
 get_page_from_freelist+0xf48/0x3530 mm/page_alloc.c:3946
 __alloc_frozen_pages_noprof+0x299/0x2dc0 mm/page_alloc.c:5304
 alloc_slab_page mm/slub.c:3266 [inline]
 allocate_slab mm/slub.c:3380 [inline]
 new_slab+0xa2/0x640 mm/slub.c:3426
 refill_objects+0xe3/0x410 mm/slub.c:7310
 refill_sheaf mm/slub.c:2804 [inline]
 __pcs_replace_empty_main+0x376/0x680 mm/slub.c:4675
 alloc_from_pcs mm/slub.c:4773 [inline]
 slab_alloc_node mm/slub.c:4905 [inline]
 __kmalloc_cache_noprof+0x479/0x6c0 mm/slub.c:5485
 _kmalloc_noprof include/linux/slab.h:988 [inline]
 _kzalloc_noprof include/linux/slab.h:1309 [inline]
 acpi_os_map_iomem+0x138/0x5e0 drivers/acpi/osl.c:353
 acpi_ex_system_memory_space_handler+0x4e8/0xbb0 drivers/acpi/acpica/exregion.c:145
 acpi_ev_address_space_dispatch+0x4d2/0xf00 drivers/acpi/acpica/evregion.c:295
 acpi_ex_access_region+0x6e1/0xe00 drivers/acpi/acpica/exfldio.c:246
 acpi_ex_field_datum_io+0x168/0xe40 drivers/acpi/acpica/exfldio.c:445
 acpi_ex_write_with_update_rule+0x2b1/0x4b0 drivers/acpi/acpica/exfldio.c:627
 acpi_ex_insert_into_field+0x672/0x870 drivers/acpi/acpica/exfldio.c:957
 acpi_ex_write_data_to_field+0x23a/0xb20 drivers/acpi/acpica/exfield.c:401
 acpi_ex_store_object_to_node+0x3f0/0x790 drivers/acpi/acpica/exstore.c:523
page_owner free stack trace missing

Memory state around the buggy address:
 ffff888022a66480: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
 ffff888022a66500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888022a66580: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
                   ^
 ffff888022a66600: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff888022a66680: fb fb fb fb fb fb fb fb 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 syzkaller@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 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

             reply	other threads:[~2026-08-20 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 14:58 syzbot [this message]
2026-08-21  3:13 ` [syzbot] KASAN: slab-use-after-free Read in vhci_send_cmd_submit Edward Adam Davis
2026-08-21  3:29   ` syzbot
2026-08-21  4:55 ` Hillf Danton
2026-08-21  5:11   ` syzbot
2026-08-21 13:08 ` [PATCH] usbip: prevent the use of unavailable urb and hcpriv in tx Edward Adam Davis
2026-08-22  0:30 ` [syzbot] KASAN: slab-use-after-free Read in vhci_send_cmd_submit Hillf Danton
2026-08-22  0:54   ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a871611.4d75e56a.c9a88.0041.GAE@google.com \
    --to=syzbot+ecbb1750082f7528b507@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox