All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3c93637d7648c24e1fd0@syzkaller.appspotmail.com>
To: axboe@kernel.dk, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] [io-uring?] memory leak in iovec_from_user (2)
Date: Mon, 10 Nov 2025 10:09:29 -0800	[thread overview]
Message-ID: <69122a59.a70a0220.22f260.00fd.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    4a0c9b339199 Merge tag 'probes-fixes-v6.18-rc4' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12af5342580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=cb128cd5cb439809
dashboard link: https://syzkaller.appspot.com/bug?extid=3c93637d7648c24e1fd0
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16af5342580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13664412580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bfd02a09ef4d/disk-4a0c9b33.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed9a1334f973/vmlinux-4a0c9b33.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e503329437ee/bzImage-4a0c9b33.xz

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

BUG: memory leak
unreferenced object 0xffff88812638cc20 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff88812638cc40 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff88812638cc60 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff88812638cc80 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff88812638cca0 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff88812638ccc0 (size 32):
  comm "syz.0.17", pid 6104, jiffies 4294942640
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4975 [inline]
    slab_alloc_node mm/slub.c:5280 [inline]
    __do_kmalloc_node mm/slub.c:5641 [inline]
    __kmalloc_noprof+0x3e3/0x6b0 mm/slub.c:5654
    kmalloc_noprof include/linux/slab.h:961 [inline]
    kmalloc_array_noprof include/linux/slab.h:1003 [inline]
    iovec_from_user lib/iov_iter.c:1309 [inline]
    iovec_from_user+0x108/0x140 lib/iov_iter.c:1292
    __import_iovec+0x71/0x350 lib/iov_iter.c:1363
    io_import_vec io_uring/rw.c:99 [inline]
    __io_import_rw_buffer+0x1e2/0x260 io_uring/rw.c:120
    io_import_rw_buffer io_uring/rw.c:139 [inline]
    io_rw_do_import io_uring/rw.c:314 [inline]
    io_prep_rw+0xb5/0x120 io_uring/rw.c:326
    io_prep_rwv io_uring/rw.c:344 [inline]
    io_prep_readv+0x20/0x80 io_uring/rw.c:359
    io_init_req io_uring/io_uring.c:2248 [inline]
    io_submit_sqe io_uring/io_uring.c:2295 [inline]
    io_submit_sqes+0x354/0xe80 io_uring/io_uring.c:2447
    __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3514
    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
    do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF


---
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:[~2025-11-10 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 18:09 syzbot [this message]
2025-11-10 20:37 ` [syzbot] [io-uring?] memory leak in iovec_from_user (2) Jens Axboe
2025-11-10 21:06   ` Jens Axboe
2025-11-10 21:34     ` Jens Axboe
2025-11-10 21:55       ` 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=69122a59.a70a0220.22f260.00fd.GAE@google.com \
    --to=syzbot+3c93637d7648c24e1fd0@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --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 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.