From: syzbot <syzbot+b197a0fb4e741cc5030e@syzkaller.appspotmail.com>
To: davem@davemloft.net, david@ixit.cz, edumazet@google.com,
horms@kernel.org, krzk@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, oe-linux-nfc@lists.linux.dev,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [usb?] [nfc?] [net?] memory leak in nci_send_cmd
Date: Sun, 30 Aug 2026 05:50:28 -0700 [thread overview]
Message-ID: <6a942714.4d659fcc.734b4.003a.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 73ae59e97596 Merge tag 'erofs-for-7.3-rc1-2' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12e70d49580000
kernel config: https://syzkaller.appspot.com/x/.config?x=563582168294b9d9
dashboard link: https://syzkaller.appspot.com/bug?extid=b197a0fb4e741cc5030e
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11df1625580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148b6979580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e5c9cbfb31a/disk-73ae59e9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/481171cf3bc4/vmlinux-73ae59e9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9df84fec3c49/bzImage-73ae59e9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b197a0fb4e741cc5030e@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88810a94e600 (size 240):
comm "syz.6.23", pid 5954, jiffies 4294942380
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 40 38 2b 81 88 ff ff 00 00 00 00 00 00 00 00 .@8+............
backtrace (crc 98a4d7):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4696 [inline]
slab_alloc_node mm/slub.c:4996 [inline]
kmem_cache_alloc_node_noprof+0x39f/0x440 mm/slub.c:5068
__alloc_skb+0xdc/0x4e0 net/core/skbuff.c:704
alloc_skb include/linux/skbuff.h:1384 [inline]
nci_skb_alloc include/net/nfc/nci_core.h:330 [inline]
nci_send_cmd+0x46/0x110 net/nfc/nci/core.c:1397
nci_reset_req net/nfc/nci/core.c:167 [inline]
__nci_request net/nfc/nci/core.c:108 [inline]
nci_open_device net/nfc/nci/core.c:503 [inline]
nci_dev_up+0x1b6/0x690 net/nfc/nci/core.c:643
nfc_dev_up+0xca/0x160 net/nfc/core.c:118
nfc_genl_dev_up+0x3d/0x70 net/nfc/netlink.c:775
genl_family_rcv_msg_doit+0x12e/0x1a0 net/netlink/genetlink.c:1114
genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline]
genl_rcv_msg+0x302/0x440 net/netlink/genetlink.c:1209
netlink_rcv_skb+0x89/0x1c0 net/netlink/af_netlink.c:2556
genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218
netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
netlink_unicast+0x38f/0x4e0 net/netlink/af_netlink.c:1345
netlink_sendmsg+0x335/0x690 net/netlink/af_netlink.c:1900
sock_sendmsg_nosec net/socket.c:800 [inline]
__sock_sendmsg net/socket.c:815 [inline]
____sys_sendmsg+0x54a/0x580 net/socket.c:2713
___sys_sendmsg+0x101/0x140 net/socket.c:2767
__sys_sendmsg+0xcd/0x140 net/socket.c:2799
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
BUG: memory leak
unreferenced object 0xffff888109c4bc80 (size 704):
comm "syz.6.23", pid 5954, jiffies 4294942380
hex dump (first 32 bytes):
20 00 01 01 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 40ddf9):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4696 [inline]
slab_alloc_node mm/slub.c:4996 [inline]
kmem_cache_alloc_node_noprof+0x39f/0x440 mm/slub.c:5068
kmalloc_reserve+0xd2/0x1b0 net/core/skbuff.c:615
__alloc_skb+0x15d/0x4e0 net/core/skbuff.c:715
alloc_skb include/linux/skbuff.h:1384 [inline]
nci_skb_alloc include/net/nfc/nci_core.h:330 [inline]
nci_send_cmd+0x46/0x110 net/nfc/nci/core.c:1397
nci_reset_req net/nfc/nci/core.c:167 [inline]
__nci_request net/nfc/nci/core.c:108 [inline]
nci_open_device net/nfc/nci/core.c:503 [inline]
nci_dev_up+0x1b6/0x690 net/nfc/nci/core.c:643
nfc_dev_up+0xca/0x160 net/nfc/core.c:118
nfc_genl_dev_up+0x3d/0x70 net/nfc/netlink.c:775
genl_family_rcv_msg_doit+0x12e/0x1a0 net/netlink/genetlink.c:1114
genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline]
genl_rcv_msg+0x302/0x440 net/netlink/genetlink.c:1209
netlink_rcv_skb+0x89/0x1c0 net/netlink/af_netlink.c:2556
genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218
netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
netlink_unicast+0x38f/0x4e0 net/netlink/af_netlink.c:1345
netlink_sendmsg+0x335/0x690 net/netlink/af_netlink.c:1900
sock_sendmsg_nosec net/socket.c:800 [inline]
__sock_sendmsg net/socket.c:815 [inline]
____sys_sendmsg+0x54a/0x580 net/socket.c:2713
___sys_sendmsg+0x101/0x140 net/socket.c:2767
__sys_sendmsg+0xcd/0x140 net/socket.c:2799
BUG: memory leak
unreferenced object 0xffff88810aa0d700 (size 240):
comm "syz.0.26", pid 5976, jiffies 4294942681
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 a0 5b 28 81 88 ff ff 00 00 00 00 00 00 00 00 ..[(............
backtrace (crc cdb4723c):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4696 [inline]
slab_alloc_node mm/slub.c:4996 [inline]
kmem_cache_alloc_node_noprof+0x39f/0x440 mm/slub.c:5068
__alloc_skb+0xdc/0x4e0 net/core/skbuff.c:704
alloc_skb include/linux/skbuff.h:1384 [inline]
nci_skb_alloc include/net/nfc/nci_core.h:330 [inline]
nci_send_cmd+0x46/0x110 net/nfc/nci/core.c:1397
nci_reset_req net/nfc/nci/core.c:167 [inline]
__nci_request net/nfc/nci/core.c:108 [inline]
nci_open_device net/nfc/nci/core.c:503 [inline]
nci_dev_up+0x1b6/0x690 net/nfc/nci/core.c:643
nfc_dev_up+0xca/0x160 net/nfc/core.c:118
nfc_genl_dev_up+0x3d/0x70 net/nfc/netlink.c:775
genl_family_rcv_msg_doit+0x12e/0x1a0 net/netlink/genetlink.c:1114
genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline]
genl_rcv_msg+0x302/0x440 net/netlink/genetlink.c:1209
netlink_rcv_skb+0x89/0x1c0 net/netlink/af_netlink.c:2556
genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218
netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
netlink_unicast+0x38f/0x4e0 net/netlink/af_netlink.c:1345
netlink_sendmsg+0x335/0x690 net/netlink/af_netlink.c:1900
sock_sendmsg_nosec net/socket.c:800 [inline]
__sock_sendmsg net/socket.c:815 [inline]
____sys_sendmsg+0x54a/0x580 net/socket.c:2713
___sys_sendmsg+0x101/0x140 net/socket.c:2767
__sys_sendmsg+0xcd/0x140 net/socket.c:2799
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
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:[~2026-08-30 12:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a942714.4d659fcc.734b4.003a.GAE@google.com \
--to=syzbot+b197a0fb4e741cc5030e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®