From: syzbot <syzbot+641eec6b7af1f62f2b99@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 io_submit_sqes (5)
Date: Mon, 01 Dec 2025 09:07:36 -0800 [thread overview]
Message-ID: <692dcb58.a70a0220.2ea503.00b5.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7d0a66e4bb90 Linux 6.18
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=110d0512580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44
dashboard link: https://syzkaller.appspot.com/bug?extid=641eec6b7af1f62f2b99
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=150d0512580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3e289f3ec7e8/disk-7d0a66e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bf695f1b8080/vmlinux-7d0a66e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb2f95cf98c6/bzImage-7d0a66e4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+641eec6b7af1f62f2b99@syzkaller.appspotmail.com
2025/12/01 16:45:07 executed programs: 5
BUG: memory leak
unreferenced object 0xffff888112d6b200 (size 248):
comm "syz.0.17", pid 6070, jiffies 4294944719
hex dump (first 32 bytes):
40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V.............
3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < ..............
backtrace (crc 9dd5d643):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4983 [inline]
kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497
__io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058
io_alloc_req io_uring/io_uring.h:543 [inline]
io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438
__do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516
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 0xffff888112e96200 (size 248):
comm "syz.0.18", pid 6072, jiffies 4294944721
hex dump (first 32 bytes):
40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V.............
3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < ..............
backtrace (crc 79b7669c):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4983 [inline]
kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497
__io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058
io_alloc_req io_uring/io_uring.h:543 [inline]
io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438
__do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516
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 0xffff888112e5ed00 (size 248):
comm "syz.0.19", pid 6073, jiffies 4294944722
hex dump (first 32 bytes):
40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V.............
3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < ..............
backtrace (crc 11e3e38b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4983 [inline]
kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497
__io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058
io_alloc_req io_uring/io_uring.h:543 [inline]
io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438
__do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516
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 0xffff888127618400 (size 248):
comm "syz.0.20", pid 6127, jiffies 4294945384
hex dump (first 32 bytes):
40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V.............
3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < ..............
backtrace (crc b9653957):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4983 [inline]
kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497
__io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058
io_alloc_req io_uring/io_uring.h:543 [inline]
io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438
__do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516
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 0xffff8881262cf200 (size 248):
comm "syz.0.21", pid 6128, jiffies 4294945385
hex dump (first 32 bytes):
40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V.............
3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < ..............
backtrace (crc 457654b1):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4983 [inline]
kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497
__io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058
io_alloc_req io_uring/io_uring.h:543 [inline]
io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438
__do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516
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
next reply other threads:[~2025-12-01 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 17:07 syzbot [this message]
2025-12-01 20:16 ` [syzbot] [io-uring?] memory leak in io_submit_sqes (5) Jens Axboe
2025-12-01 21:00 ` syzbot
2025-12-01 20:36 ` shaurya
2025-12-01 21:24 ` syzbot
2025-12-01 21:29 ` Jens Axboe
2025-12-01 21:31 ` Jens Axboe
2025-12-01 21:52 ` 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=692dcb58.a70a0220.2ea503.00b5.GAE@google.com \
--to=syzbot+641eec6b7af1f62f2b99@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox