From: syzbot <syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] memory leak in gsm_activate_mux
Date: Mon, 06 Jul 2026 06:55:01 -0700 [thread overview]
Message-ID: <6a4bb3b5.b42ede87.8bd1.0028.GAE@google.com> (raw)
In-Reply-To: <275ed678-5216-4d1c-bcff-22b63e689587@yandex.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in gsm_activate_mux
BUG: memory leak
unreferenced object 0xffff8881035efc00 (size 1024):
comm "syz-executor.0", pid 5304, jiffies 4294943119
hex dump (first 32 bytes):
00 0c 9c 08 81 88 ff ff 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 c142557c):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4625 [inline]
slab_alloc_node mm/slub.c:4945 [inline]
__kmalloc_cache_noprof+0x356/0x440 mm/slub.c:5511
_kmalloc_noprof include/linux/slab.h:969 [inline]
_kzalloc_noprof include/linux/slab.h:1290 [inline]
gsm_dlci_alloc+0x29/0x1b0 drivers/tty/n_gsm.c:2648
gsm_activate_mux+0x1a/0x1a0 drivers/tty/n_gsm.c:3189
gsm_config_ext drivers/tty/n_gsm.c:3494 [inline]
gsmld_ioctl+0x1b8/0x9e0 drivers/tty/n_gsm.c:3858
tty_ioctl+0xabc/0xd50 drivers/tty/tty_io.c:2801
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x5f/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x76/0x7e
BUG: memory leak
unreferenced object 0xffff888109829c00 (size 1024):
comm "syz-executor.0", pid 5396, jiffies 4294943679
hex dump (first 32 bytes):
00 ec 2f 03 81 88 ff ff 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 2f81146e):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4625 [inline]
slab_alloc_node mm/slub.c:4945 [inline]
__kmalloc_cache_noprof+0x356/0x440 mm/slub.c:5511
_kmalloc_noprof include/linux/slab.h:969 [inline]
_kzalloc_noprof include/linux/slab.h:1290 [inline]
gsm_dlci_alloc+0x29/0x1b0 drivers/tty/n_gsm.c:2648
gsm_activate_mux+0x1a/0x1a0 drivers/tty/n_gsm.c:3189
gsm_config_ext drivers/tty/n_gsm.c:3494 [inline]
gsmld_ioctl+0x1b8/0x9e0 drivers/tty/n_gsm.c:3858
tty_ioctl+0xabc/0xd50 drivers/tty/tty_io.c:2801
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x5f/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x76/0x7e
Tested on:
commit: 8cdeaa50 Linux 7.2-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16c82b39580000
kernel config: https://syzkaller.appspot.com/x/.config?x=83d5b4d9fb5a5039
dashboard link: https://syzkaller.appspot.com/bug?extid=b5d1f455d385b2c7da3c
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-06 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <275ed678-5216-4d1c-bcff-22b63e689587@yandex.ru>
2026-07-06 13:55 ` syzbot [this message]
[not found] <1cea0f5e-32e1-4b01-b087-1e00f6fc976e@yandex.ru>
2026-07-06 15:07 ` [syzbot] [serial?] memory leak in gsm_activate_mux syzbot
2026-04-22 17:37 [PATCH] tty: n_gsm: fix " Minu Jin
2026-04-22 18:04 ` [syzbot] [serial?] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 6:29 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=6a4bb3b5.b42ede87.8bd1.0028.GAE@google.com \
--to=syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--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