From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f79.google.com (mail-oo1-f79.google.com [209.85.161.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2905317A309 for ; Fri, 7 Aug 2026 00:01:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.79 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786060896; cv=none; b=tyPVbkAoM0To6qzzTekKe9tC8F6MYm0yEsKJxjiQ5Bsn7mTTZHPnQXAhqtltEAjqPPUGmd4vLDanFwTjPk6mAg697xkGSUBPhWjElGqSf1xp2iiRZZpcq4TYHYZ0F/ZhaeR8T2gTn1lKNrg6gxiRDfL6Q3MIR1Sn36DqndEsXrk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786060896; c=relaxed/simple; bh=0p++SH2CILQuvhFqp1xYlCloedFp4jotXW/kLYZMCr8=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=BUqvvZhBcsly7LncgQc9OFeTx7b+vdoCgKSdMeH0CAn29AJRaYDjt0cRI/ENzGEl81T+tJCiv9Q1Y3n7H6/Yl3iWd6d+md6q4rww0JFSOKN2PjERBT4kJH7ayAKPFjPkTAfk7wn/YFd3v+Ax4CJa/epFKKCSqWvnZUShY0ZsoQo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.79 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f79.google.com with SMTP id 006d021491bc7-6b026a31eb9so261422eaf.1 for ; Thu, 06 Aug 2026 17:01:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786060893; x=1786665693; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=DHl/omsnQZWAsLsuqjcopC+CiqjuXwfHPzn9WjLQBxs=; b=EqR3yCesfyFfp/KMtb6ch6iT1C8JSNnDrKjykA4xGFKzlupBuDYg2mwnpJaL627Izr 3Anp9UsFhBW9Q3TgrTa35cGhyQo8UtMOZOo7E2eU8FzMhJnORCiZan2bf2DY2duzA43P wRWPX8laeGf+bS0cZr40r8W0u8z96Ad6IZT+TeR6KMEEZZ2k3AZBuodrCh5XRBJ6xOER rFG5ducWIkT4SRb4kndsrnKCjeA90Qac4kBcIX1Q2ZYsqh2vYRdsXsyAfwGvcsnyxlVi iUPVZW4U4FggWd5Y4Yw7sImiQickzO8sc9ys7PjcKneWaY1Dc/7e5E78UMOPXBJU9eif tvdA== X-Forwarded-Encrypted: i=1; AHgh+RpCa0GLIbHzo9dCeXAADDl004eWWKSSM4YxpReRqEuLe4Fy27FEAP7BsdgmmDB8IBurtcae/OqSWwCV1cE=@vger.kernel.org X-Gm-Message-State: AOJu0YzRz4b7KkiNBNk49vjSbHeyxv3K0dD9NQKI0TLcxy41X+C7fZHg 3y9FMPIdqdakO6nq/xeNWZ0e/F1G/JZi0TVFN+id70ERIWHKozhkGscdEL6DvvTkewJhcvDh41A v6VRAfaEOKVk6FVvTyBZQ9i9Rf6cf8tMoHKI1pXqBTVlXjZ21lkhzDRse1Cc= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:f024:b0:6af:f3a3:7f5d with SMTP id 006d021491bc7-6aff3a486f6mr4081871eaf.26.1786060892795; Thu, 06 Aug 2026 17:01:32 -0700 (PDT) Date: Thu, 06 Aug 2026 17:01:32 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a75205c.01d0871a.3a0d52.0033.GAE@google.com> Subject: [syzbot] [nvme?] KASAN: slab-out-of-bounds Read in nvmet_install_queue From: syzbot To: hch@lst.de, kch@nvidia.com, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, sagi@grimberg.me, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 848acc8ffe1b Merge tag 'fsverity-for-linus' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12cb8bb9580000 kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782 dashboard link: https://syzkaller.appspot.com/bug?extid=2626e846cd2585c9aa67 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-848acc8f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/6fb497cc0c8d/vmlinux-848acc8f.xz kernel image: https://storage.googleapis.com/syzbot-assets/663ccee34982/bzImage-848acc8f.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2626e846cd2585c9aa67@syzkaller.appspotmail.com ================================================================== BUG: KASAN: slab-out-of-bounds in nvmet_install_queue+0x522/0x590 drivers/nvme/target/fabrics-cmd.c:189 Read of size 8 at addr ffff888058219a70 by task kworker/u33:8/1166 CPU: 1 UID: 0 PID: 1166 Comm: kworker/u33:8 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 Workqueue: nvmet-wq nvme_loop_execute_work Call Trace: __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 nvmet_install_queue+0x522/0x590 drivers/nvme/target/fabrics-cmd.c:189 nvmet_execute_io_connect+0x294/0x490 drivers/nvme/target/fabrics-cmd.c:380 process_one_work+0xa23/0x1940 kernel/workqueue.c:3322 process_scheduled_works kernel/workqueue.c:3405 [inline] worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486 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 Allocated by task 1174: 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] _kzalloc_noprof include/linux/slab.h:1309 [inline] nvmet_alloc_ctrl+0x9c2/0x1560 drivers/nvme/target/core.c:1655 nvmet_execute_admin_connect+0x3c3/0x5b0 drivers/nvme/target/fabrics-cmd.c:317 process_one_work+0xa23/0x1940 kernel/workqueue.c:3322 process_scheduled_works kernel/workqueue.c:3405 [inline] worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486 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 The buggy address belongs to the object at ffff888058219a60 which belongs to the cache kmalloc-16 of size 16 The buggy address is located 0 bytes to the right of allocated 16-byte region [ffff888058219a60, ffff888058219a70) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888058219f80 pfn:0x58219 flags: 0xfff00000000200(workingset|node=0|zone=1|lastcpupid=0x7ff) page_type: f5(slab) raw: 00fff00000000200 ffff88801bc42640 ffffea000169a050 ffffea00015fa390 raw: ffff888058219f80 000000080080007f 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 5739, tgid 5739 (syz-executor), ts 50610714726, free_ts 49976327990 create_dummy_stack mm/page_owner.c:103 [inline] register_dummy_stack+0x74/0xb0 mm/page_owner.c:109 init_page_owner+0x42/0xa10 mm/page_owner.c:127 invoke_init_callbacks mm/page_ext.c:152 [inline] page_ext_init+0x71d/0x780 mm/page_ext.c:490 mm_core_init+0x229/0x270 mm/mm_init.c:2748 page last free pid 33 tgid 33 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] __free_pages_prepare mm/page_alloc.c:1406 [inline] __free_frozen_pages+0x79f/0x1090 mm/page_alloc.c:2950 __pagetable_free include/linux/mm.h:3695 [inline] pagetable_free include/linux/mm.h:3719 [inline] pagetable_dtor_free include/linux/mm.h:3818 [inline] __tlb_remove_table include/asm-generic/tlb.h:221 [inline] __tlb_remove_table_free mm/mmu_gather.c:228 [inline] tlb_remove_table_rcu+0x2cf/0x380 mm/mmu_gather.c:291 rcu_do_batch kernel/rcu/tree.c:2645 [inline] rcu_core+0x5a2/0x10d0 kernel/rcu/tree.c:2897 handle_softirqs+0x1ea/0x9b0 kernel/softirq.c:622 run_ksoftirqd kernel/softirq.c:1076 [inline] run_ksoftirqd+0x38/0x60 kernel/softirq.c:1068 smpboot_thread_fn+0x3d3/0xaa0 kernel/smpboot.c:160 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 Memory state around the buggy address: ffff888058219900: fa fb fc fc fa fb fc fc fa fb fc fc fa fb fc fc ffff888058219980: fa fb fc fc fa fb fc fc fa fb fc fc 00 02 fc fc >ffff888058219a00: 00 00 fc fc fa fb fc fc fa fb fc fc 00 00 fc fc ^ ffff888058219a80: fa fb fc fc fa fb fc fc fa fb fc fc 00 00 fc fc ffff888058219b00: 00 00 fc fc 00 00 fc fc 00 00 fc fc 00 00 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 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