From: syzbot <syzbot+1b2c9c4a0f8708082678@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, phind.uet@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [virt?] memory leak in __vsock_create (2)
Date: Sun, 19 Jul 2026 00:47:01 -0700 [thread overview]
Message-ID: <6a5c80f5.f1649fcc.2a4208.03d8.GAE@google.com> (raw)
In-Reply-To: <CAL5WHMJO_s-xs5W-KVKJdVPf4FzVzapR1g0Q-wJayTk+b3-WZA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in __vsock_create
2026/07/19 07:45:48 executed programs: 5
BUG: memory leak
unreferenced object 0xffff888113812d00 (size 1272):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
28 00 0b 40 00 00 00 00 00 00 00 00 00 00 00 00 (..@............
backtrace (crc 3df84e77):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
kmem_cache_alloc_noprof+0x388/0x410 mm/slub.c:4907
sk_prot_alloc+0x3e/0x1b0 net/core/sock.c:2246
sk_alloc+0x36/0x3d0 net/core/sock.c:2308
__vsock_create.constprop.0+0x38/0x2f0 net/vmw_vsock/af_vsock.c:919
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1555 [inline]
virtio_transport_recv_pkt+0x904/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff888117aa8980 (size 32):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
f8 52 0a 00 81 88 ff ff 00 00 00 00 00 00 00 00 .R..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 42a7bc0e):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
__do_kmalloc_node mm/slub.c:5310 [inline]
__kmalloc_noprof+0x3f8/0x540 mm/slub.c:5336
_kmalloc_noprof include/linux/slab.h:988 [inline]
_kzalloc_noprof include/linux/slab.h:1305 [inline]
lsm_blob_alloc+0x4d/0x80 security/security.c:218
lsm_sock_alloc security/security.c:4477 [inline]
security_sk_alloc+0x2d/0x290 security/security.c:4493
sk_prot_alloc+0x8f/0x1b0 net/core/sock.c:2255
sk_alloc+0x36/0x3d0 net/core/sock.c:2308
__vsock_create.constprop.0+0x38/0x2f0 net/vmw_vsock/af_vsock.c:919
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1555 [inline]
virtio_transport_recv_pkt+0x904/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff8881122fe5a0 (size 96):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
00 2d 81 13 81 88 ff ff 00 00 00 00 00 00 00 00 .-..............
00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 ................
backtrace (crc 159c7144):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
__kmalloc_cache_noprof+0x38c/0x420 mm/slub.c:5456
_kmalloc_noprof include/linux/slab.h:984 [inline]
_kzalloc_noprof include/linux/slab.h:1305 [inline]
virtio_transport_do_socket_init+0x2b/0xf0 net/vmw_vsock/virtio_transport_common.c:907
vsock_assign_transport+0x3a3/0x460 net/vmw_vsock/af_vsock.c:670
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1571 [inline]
virtio_transport_recv_pkt+0x95c/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff888113812800 (size 1272):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
28 00 0b 40 00 00 00 00 00 00 00 00 00 00 00 00 (..@............
backtrace (crc 4993b404):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
kmem_cache_alloc_noprof+0x388/0x410 mm/slub.c:4907
sk_prot_alloc+0x3e/0x1b0 net/core/sock.c:2246
sk_alloc+0x36/0x3d0 net/core/sock.c:2308
__vsock_create.constprop.0+0x38/0x2f0 net/vmw_vsock/af_vsock.c:919
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1555 [inline]
virtio_transport_recv_pkt+0x904/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff888117aa8320 (size 32):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
f8 52 0a 00 81 88 ff ff 00 00 00 00 00 00 00 00 .R..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 42a7bc0e):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
__do_kmalloc_node mm/slub.c:5310 [inline]
__kmalloc_noprof+0x3f8/0x540 mm/slub.c:5336
_kmalloc_noprof include/linux/slab.h:988 [inline]
_kzalloc_noprof include/linux/slab.h:1305 [inline]
lsm_blob_alloc+0x4d/0x80 security/security.c:218
lsm_sock_alloc security/security.c:4477 [inline]
security_sk_alloc+0x2d/0x290 security/security.c:4493
sk_prot_alloc+0x8f/0x1b0 net/core/sock.c:2255
sk_alloc+0x36/0x3d0 net/core/sock.c:2308
__vsock_create.constprop.0+0x38/0x2f0 net/vmw_vsock/af_vsock.c:919
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1555 [inline]
virtio_transport_recv_pkt+0x904/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
BUG: memory leak
unreferenced object 0xffff88811756a000 (size 96):
comm "kworker/1:2", pid 3105, jiffies 4294947499
hex dump (first 32 bytes):
00 28 81 13 81 88 ff ff 00 00 00 00 00 00 00 00 .(..............
00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 ................
backtrace (crc 87703aa0):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4593 [inline]
slab_alloc_node mm/slub.c:4893 [inline]
__kmalloc_cache_noprof+0x38c/0x420 mm/slub.c:5456
_kmalloc_noprof include/linux/slab.h:984 [inline]
_kzalloc_noprof include/linux/slab.h:1305 [inline]
virtio_transport_do_socket_init+0x2b/0xf0 net/vmw_vsock/virtio_transport_common.c:907
vsock_assign_transport+0x3a3/0x460 net/vmw_vsock/af_vsock.c:670
virtio_transport_recv_listen net/vmw_vsock/virtio_transport_common.c:1571 [inline]
virtio_transport_recv_pkt+0x95c/0xf80 net/vmw_vsock/virtio_transport_common.c:1681
vsock_loopback_work+0x104/0x140 net/vmw_vsock/vsock_loopback.c:142
process_one_work+0x2b8/0x600 kernel/workqueue.c:3375
process_scheduled_works kernel/workqueue.c:3458 [inline]
worker_thread+0x255/0x4a0 kernel/workqueue.c:3539
kthread+0x14e/0x1a0 kernel/kthread.c:436
ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
Tested on:
commit: 0718283a Add linux-next specific files for 20260717
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13c222b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f74727dd1edec112
dashboard link: https://syzkaller.appspot.com/bug?extid=1b2c9c4a0f8708082678
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Note: no patches were applied.
next parent reply other threads:[~2026-07-19 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL5WHMJO_s-xs5W-KVKJdVPf4FzVzapR1g0Q-wJayTk+b3-WZA@mail.gmail.com>
2026-07-19 7:47 ` syzbot [this message]
[not found] <CAL5WHMLML-5+Jd1BO2vEm=+TyCSohZO-+4uQPJ3MJiwjHZqZGw@mail.gmail.com>
2026-07-19 9: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=6a5c80f5.f1649fcc.2a4208.03d8.GAE@google.com \
--to=syzbot+1b2c9c4a0f8708082678@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phind.uet@gmail.com \
--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
Powered by JetHome