From: Joas Antonio dos Santos via B4 Relay <devnull+joasantonio108.gmail.com@kernel.org>
To: joasantonio108@gmail.com, david@ixit.cz, krzk@kernel.org
Cc: oe-linux-nfc@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org
Subject: [PATCH RESEND v2 2/2] nfc: st21nfca: prevent double completion of SE APDU request
Date: Tue, 10 Nov 2026 03:22:56 +0000 [thread overview]
Message-ID: <20261110-st21nfca-v2-v2-2-cf9102b314cb@gmail.com> (raw)
In-Reply-To: <20261110-st21nfca-v2-v2-0-cf9102b314cb@gmail.com>
From: Joas Antonio dos Santos <joasantonio108@gmail.com>
Use the spinlock added in the previous commit to prevent completing an
SE APDU request more than once. Without this, the timeout work handler
(st21nfca_se_wt_work) and the EVT_TRANSMIT_DATA event handler can race
and both invoke the callback, leading to a use-after-free or double-free
of the callback context.
Check bwi_active under the lock in both completion paths and bail out if
the request was already completed. Also reject a new SE APDU request in
st21nfca_hci_se_io() while one is already in progress by returning
-EBUSY.
Found by LLM-assisted manual code review.
Fixes: 2130fb97fecf ("NFC: st21nfca: Adding support for secure element")
Cc: Simon Horman <horms@kernel.org>
Signed-off-by: Joas Antonio dos Santos <joasantonio108@gmail.com>
---
drivers/nfc/st21nfca/se.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/nfc/st21nfca/se.c b/drivers/nfc/st21nfca/se.c
index 03a30f797ff8..3be77420e956 100644
--- a/drivers/nfc/st21nfca/se.c
+++ b/drivers/nfc/st21nfca/se.c
@@ -228,6 +228,10 @@ int st21nfca_hci_se_io(struct nfc_hci_dev *hdev, u32 se_idx,
switch (se_idx) {
case ST21NFCA_ESE_HOST_ID:
spin_lock(&info->se_info.se_lock);
+ if (info->se_info.bwi_active) {
+ spin_unlock(&info->se_info.se_lock);
+ return -EBUSY;
+ }
info->se_info.cb = cb;
info->se_info.cb_context = cb_context;
info->se_info.bwi_active = true;
@@ -269,6 +273,10 @@ static void st21nfca_se_wt_work(struct work_struct *work)
se_info.timeout_work);
spin_lock(&info->se_info.se_lock);
+ if (!info->se_info.bwi_active) {
+ spin_unlock(&info->se_info.se_lock);
+ return;
+ }
info->se_info.bwi_active = false;
cb = info->se_info.cb;
cb_context = info->se_info.cb_context;
@@ -395,6 +403,10 @@ int st21nfca_apdu_reader_event_received(struct nfc_hci_dev *hdev,
cancel_work_sync(&info->se_info.timeout_work);
spin_lock(&info->se_info.se_lock);
+ if (!info->se_info.bwi_active) {
+ spin_unlock(&info->se_info.se_lock);
+ break;
+ }
info->se_info.bwi_active = false;
cb = info->se_info.cb;
cb_context = info->se_info.cb_context;
--
2.43.0
prev parent reply other threads:[~2026-11-10 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 3:22 [PATCH RESEND v2 0/2] nfc: st21nfca: fix SE APDU request race condition Joas Antonio dos Santos via B4 Relay
2026-11-10 3:22 ` [PATCH RESEND v2 1/2] nfc: st21nfca: add spinlock to serialize SE APDU request state Joas Antonio dos Santos via B4 Relay
2026-11-10 3:22 ` Joas Antonio dos Santos via B4 Relay [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=20261110-st21nfca-v2-v2-2-cf9102b314cb@gmail.com \
--to=devnull+joasantonio108.gmail.com@kernel.org \
--cc=david@ixit.cz \
--cc=horms@kernel.org \
--cc=joasantonio108@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
/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®