From: Shubham Antil <shubham@octane.security>
To: netdev@vger.kernel.org
Cc: oe-linux-nfc@lists.linux.dev, David Heidelberg <david@ixit.cz>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org,
Giovanni Vignone <gio@octane.security>
Subject: [PATCH v4 1/2] nfc: nfcmrvl: set drv_data before registering the nci device
Date: Tue, 6 Oct 2026 17:25:30 +0530 [thread overview]
Message-ID: <20261006115532.72100-2-shubham@octane.security> (raw)
In-Reply-To: <20261006115532.72100-1-shubham@octane.security>
nfcmrvl_nci_uart_open() stores the per-ldisc back-pointer nu->drv_data
only after nfcmrvl_nci_register_dev() has returned. That function
registers the nci device, and a transmit started during registration
reaches the UART write path
nci_uart_write_work() -> nu->ops.tx_start()
== nfcmrvl_nci_uart_tx_start()
which dereferences nu->drv_data:
struct nfcmrvl_private *priv = (struct nfcmrvl_private *)nu->drv_data;
if (priv->ndev->nfc_dev->fw_download_in_progress)
At that point nu->drv_data is still NULL:
BUG: KASAN: null-ptr-deref in nfcmrvl_nci_uart_tx_start+0x2c/0xc0
Workqueue: events nci_uart_write_work
Call Trace:
nfcmrvl_nci_uart_tx_start
nci_uart_write_work
worker_thread
Publish nu->drv_data (and nu->ndev) for the UART phy before
nci_register_device() is called, and clear them again if registration
fails, so that a transmit triggered during registration finds a valid
pointer. The now-redundant assignment in nfcmrvl_nci_uart_open() is
removed.
Fixes: e097dc624f78 ("NFC: nfcmrvl: add UART driver")
Assisted-by: LLM Claude
Signed-off-by: Shubham Antil <shubham@octane.security>
---
drivers/nfc/nfcmrvl/main.c | 17 +++++++++++++++++
drivers/nfc/nfcmrvl/uart.c | 3 ---
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/nfc/nfcmrvl/main.c b/drivers/nfc/nfcmrvl/main.c
index 6efa83219..8186e86d7 100644
--- a/drivers/nfc/nfcmrvl/main.c
+++ b/drivers/nfc/nfcmrvl/main.c
@@ -96,6 +96,7 @@ struct nfcmrvl_private *nfcmrvl_nci_register_dev(enum nfcmrvl_phy phy,
const struct nfcmrvl_platform_data *pdata)
{
struct nfcmrvl_private *priv;
+ struct nci_uart *nu = NULL;
int rc;
int headroom;
int tailroom;
@@ -110,6 +111,9 @@ struct nfcmrvl_private *nfcmrvl_nci_register_dev(enum nfcmrvl_phy phy,
priv->dev = dev;
priv->phy = phy;
+ if (phy == NFCMRVL_PHY_UART)
+ nu = drv_data;
+
memcpy(&priv->config, pdata, sizeof(*pdata));
if (!priv->config.reset_gpio) {
@@ -154,9 +158,22 @@ struct nfcmrvl_private *nfcmrvl_nci_register_dev(enum nfcmrvl_phy phy,
nci_set_drvdata(priv->ndev, priv);
+ /* For the UART phy the transmit path reaches the driver through
+ * nu->drv_data; publish it before nci_register_device() so a transmit
+ * triggered during registration does not dereference a NULL pointer.
+ */
+ if (nu) {
+ nu->drv_data = priv;
+ nu->ndev = priv->ndev;
+ }
+
rc = nci_register_device(priv->ndev);
if (rc) {
nfc_err(dev, "nci_register_device failed %d\n", rc);
+ if (nu) {
+ nu->drv_data = NULL;
+ nu->ndev = NULL;
+ }
goto error_fw_dnld_deinit;
}
diff --git a/drivers/nfc/nfcmrvl/uart.c b/drivers/nfc/nfcmrvl/uart.c
index 9aedd1687..421e6dc99 100644
--- a/drivers/nfc/nfcmrvl/uart.c
+++ b/drivers/nfc/nfcmrvl/uart.c
@@ -138,9 +138,6 @@ static int nfcmrvl_nci_uart_open(struct nci_uart *nu)
priv->support_fw_dnld = true;
- nu->drv_data = priv;
- nu->ndev = priv->ndev;
-
return 0;
}
--
2.43.0
next prev parent reply other threads:[~2026-10-06 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 11:55 [PATCH v4 0/2] nfc: nci: uart: fix write_work teardown UAF (+ nfcmrvl drv_data) Shubham Antil
2026-10-06 11:55 ` Shubham Antil [this message]
2026-10-06 11:55 ` [PATCH v4 2/2] nfc: nci: uart: fix use-after-free of write_work on ldisc teardown Shubham Antil
2026-10-09 5:55 ` netdev-bot+sashiko
2026-10-06 11:59 ` [PATCH v4 0/2] nfc: nci: uart: fix write_work teardown UAF (+ nfcmrvl drv_data) netdev-bot+sinfo
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=20261006115532.72100-2-shubham@octane.security \
--to=shubham@octane.security \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=edumazet@google.com \
--cc=gio@octane.security \
--cc=horms@kernel.org \
--cc=johan@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 \
/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®