From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
To: syzbot <syzbot+b197a0fb4e741cc5030e@syzkaller.appspotmail.com>
Cc: 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: Re: [syzbot] [usb?] [nfc?] [net?] memory leak in nci_send_cmd
Date: Sun, 30 Aug 2026 21:54:19 +0530 [thread overview]
Message-ID: <apRZM5ZkGw7KQq4-@user> (raw)
In-Reply-To: <6a942714.4d659fcc.734b4.003a.GAE@google.com>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 73ae59e975966d24e32926247ddb45a537ebe184
diff --git a/drivers/nfc/nfcmrvl/usb.c b/drivers/nfc/nfcmrvl/usb.c
index c7f2afe00b93..7a4094797ba4 100644
--- a/drivers/nfc/nfcmrvl/usb.c
+++ b/drivers/nfc/nfcmrvl/usb.c
@@ -224,12 +224,16 @@ static int nfcmrvl_usb_nci_send(struct nfcmrvl_private *priv,
unsigned int pipe;
int err;
- if (!drv_data->bulk_tx_ep)
+ if (!drv_data->bulk_tx_ep) {
+ kfree_skb(skb);
return -ENODEV;
+ }
urb = usb_alloc_urb(0, GFP_ATOMIC);
- if (!urb)
+ if (!urb) {
+ kfree_skb(skb);
return -ENOMEM;
+ }
pipe = usb_sndbulkpipe(drv_data->udev,
drv_data->bulk_tx_ep->bEndpointAddress);
@@ -254,6 +258,7 @@ static int nfcmrvl_usb_nci_send(struct nfcmrvl_private *priv,
"urb %p submission failed (%d)\n", urb, -err);
kfree(urb->setup_packet);
usb_unanchor_urb(urb);
+ kfree_skb(skb);
} else {
usb_mark_last_busy(drv_data->udev);
}
next prev parent reply other threads:[~2026-08-30 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 12:50 [syzbot] [usb?] [nfc?] [net?] memory leak in nci_send_cmd syzbot
2026-08-30 16:24 ` Yalagada Pavan Kumar [this message]
2026-08-30 17:10 ` 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=apRZM5ZkGw7KQq4-@user \
--to=pavankumaryalagada@gmail.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=syzbot+b197a0fb4e741cc5030e@syzkaller.appspotmail.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 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.