From: syzbot <syzbot+df28076a30d726933015@syzkaller.appspotmail.com>
To: iommu@lists.linux.dev, jgg@ziepe.ca, joro@8bytes.org,
kevin.tian@intel.com, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: [syzbot] [iommu?] KMSAN: uninit-value in pfn_reader_next
Date: Fri, 23 Jan 2026 22:45:26 -0800 [thread overview]
Message-ID: <69746a86.050a0220.226181.0002.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c072629f05d7 Merge tag 'v6.19-p4' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1716005a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8bf02b9e495b9fcd
dashboard link: https://syzkaller.appspot.com/bug?extid=df28076a30d726933015
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1436b79a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a63d22580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b6b938ba4a72/disk-c072629f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bb1384b011b2/vmlinux-c072629f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1dd4bb2f206e/bzImage-c072629f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df28076a30d726933015@syzkaller.appspotmail.com
iommufd_mock iommufd_mock0: Adding to iommu group 0
=====================================================
BUG: KMSAN: uninit-value in batch_add_pfn_num drivers/iommu/iommufd/pages.c:365 [inline]
BUG: KMSAN: uninit-value in batch_add_pfn drivers/iommu/iommufd/pages.c:398 [inline]
BUG: KMSAN: uninit-value in batch_from_pages drivers/iommu/iommufd/pages.c:658 [inline]
BUG: KMSAN: uninit-value in pfn_reader_fill_span drivers/iommu/iommufd/pages.c:1220 [inline]
BUG: KMSAN: uninit-value in pfn_reader_next+0x1d5a/0x3e50 drivers/iommu/iommufd/pages.c:1247
batch_add_pfn_num drivers/iommu/iommufd/pages.c:365 [inline]
batch_add_pfn drivers/iommu/iommufd/pages.c:398 [inline]
batch_from_pages drivers/iommu/iommufd/pages.c:658 [inline]
pfn_reader_fill_span drivers/iommu/iommufd/pages.c:1220 [inline]
pfn_reader_next+0x1d5a/0x3e50 drivers/iommu/iommufd/pages.c:1247
pfn_reader_first+0xbcf/0xee0 drivers/iommu/iommufd/pages.c:1354
iopt_area_fill_domains+0x202/0x1590 drivers/iommu/iommufd/pages.c:1917
iopt_fill_domains_pages drivers/iommu/iommufd/io_pagetable.c:359 [inline]
iopt_map_pages+0x1ba5/0x2130 drivers/iommu/iommufd/io_pagetable.c:387
iopt_map_common+0x224/0x610 drivers/iommu/iommufd/io_pagetable.c:425
iopt_map_user_pages+0x148/0x1c0 drivers/iommu/iommufd/io_pagetable.c:466
iommufd_ioas_map+0x6a2/0x9b0 drivers/iommu/iommufd/ioas.c:270
iommufd_fops_ioctl+0x82a/0x9e0 drivers/iommu/iommufd/main.c:533
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0x23c/0x400 fs/ioctl.c:583
__x64_sys_ioctl+0x97/0xe0 fs/ioctl.c:583
x64_sys_call+0x18a7/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Local variable pfns created at:
iopt_area_fill_domains+0x5c/0x1590 drivers/iommu/iommufd/pages.c:1900
iopt_fill_domains_pages drivers/iommu/iommufd/io_pagetable.c:359 [inline]
iopt_map_pages+0x1ba5/0x2130 drivers/iommu/iommufd/io_pagetable.c:387
CPU: 0 UID: 0 PID: 6065 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/13/2026
=====================================================
---
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
next reply other threads:[~2026-01-24 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 6:45 syzbot [this message]
2026-01-24 9:07 ` Forwarded: [PATCH] iommufd: Initialize pfn_reader in iopt_area_fill_domains() syzbot
2026-01-24 11:24 ` Forwarded: [PATCH] iommufd: Initialize batch structures in map/unmap paths syzbot
2026-01-24 12:46 ` Forwarded: [PATCH] iommufd: Initialize batch->kind in batch_clear() syzbot
[not found] <20260124090709.617302-1-kartikey406@gmail.com>
2026-01-24 10:25 ` [syzbot] [iommu?] KMSAN: uninit-value in pfn_reader_next syzbot
[not found] <20260124112446.618792-1-kartikey406@gmail.com>
2026-01-24 12:20 ` syzbot
[not found] <20260124124617.623091-1-kartikey406@gmail.com>
2026-01-24 13:18 ` 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=69746a86.050a0220.226181.0002.GAE@google.com \
--to=syzbot+df28076a30d726933015@syzkaller.appspotmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.