From: Wentao Liang <vulab@iscas.ac.cn>
To: davem@davemloft.net
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,
Wentao Liang <vulab@iscas.ac.cn>,
stable@vger.kernel.org
Subject: [PATCH] nfc: llcp: Fix socket reference leak in nfc_llcp_recv_ui()
Date: Wed, 16 Sep 2026 07:34:24 +0000 [thread overview]
Message-ID: <20260916073424.1971784-1-vulab@iscas.ac.cn> (raw)
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);
--
2.34.1
next reply other threads:[~2026-09-16 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 7:34 Wentao Liang [this message]
2026-09-16 8:37 ` [PATCH] nfc: llcp: Fix socket reference leak in nfc_llcp_recv_ui() Xuanqiang Luo
2026-09-20 7:48 ` netdev-bot+sashiko
2026-09-25 9:04 ` Simon Horman
2026-09-21 15:11 ` krzk
2026-09-21 15:12 ` krzk
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=20260916073424.1971784-1-vulab@iscas.ac.cn \
--to=vulab@iscas.ac.cn \
--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 \
/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