From: Xuanqiang Luo <xuanqiang.luo@linux.dev>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: david+nfc@ixit.cz, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, oe-linux-nfc@lists.linux.dev,
pabeni@redhat.com, sameo@linux.intel.com, stable@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] nfc: llcp: Fix socket reference leak in nfc_llcp_recv_ui()
Date: Wed, 16 Sep 2026 16:37:29 +0800 [thread overview]
Message-ID: <c45fe13e-0879-4848-b66d-b95c49a906a6@linux.dev> (raw)
In-Reply-To: <20260916073424.1971784-1-vulab@iscas.ac.cn>
在 2026/9/16 15:34, Wentao Liang 写道:
> In nfc_llcp_recv_ui(), nfc_llcp_sock_get() is called to find the bound
> socket. If the socket type is not SOCK_DGRAM, the function returns
> directly without releasing the socket reference via nfc_llcp_sock_put(),
> resulting in a reference count leak.
>
> Add nfc_llcp_sock_put() when the socket type is not SOCK_DGRAM.
>
> Fixes: 968272bf0087 ("NFC: Handle LLCP UI frames")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> net/nfc/llcp_core.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/net/nfc/llcp_core.c b/net/nfc/llcp_core.c
> index db5bc6a878dd..5813c80ca593 100644
> --- a/net/nfc/llcp_core.c
> +++ b/net/nfc/llcp_core.c
> @@ -888,8 +888,12 @@ static void nfc_llcp_recv_ui(struct nfc_llcp_local *local,
>
> /* We're looking for a bound socket, not a client one */
> llcp_sock = nfc_llcp_sock_get(local, dsap, LLCP_SAP_SDP);
> - if (llcp_sock == NULL || llcp_sock->sk.sk_type != SOCK_DGRAM)
> + if (!llcp_sock)
> return;
> + if (llcp_sock->sk.sk_type != SOCK_DGRAM) {
> + nfc_llcp_sock_put(llcp_sock);
> + return;
> + }
>
> /* There is no sequence with UI frames */
> skb_pull(skb, LLCP_HEADER_SIZE);
Reviewed-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
Please use the [PATCH net] subject prefix for fixes targeting the net
tree. See the netdev submission guidelines:
https://docs.kernel.org/process/maintainer-netdev.html#networking-subsystem-netdev
Thanks,
Xuanqiang
prev parent reply other threads:[~2026-09-16 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 7:34 Wentao Liang
2026-09-16 8:37 ` Xuanqiang Luo [this message]
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=c45fe13e-0879-4848-b66d-b95c49a906a6@linux.dev \
--to=xuanqiang.luo@linux.dev \
--cc=davem@davemloft.net \
--cc=david+nfc@ixit.cz \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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®