From: "Ömer Mete Kaya" <omermetekaya0@gmail.com>
To: oe-linux-nfc@lists.linux.dev
Cc: david@ixit.cz, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ömer Mete Kaya" <omermetekaya0@gmail.com>
Subject: [PATCH net v2] nfc: nci: fix out-of-bounds read in nci_core_reset_rsp_packet()
Date: Mon, 5 Oct 2026 16:26:28 +0300 [thread overview]
Message-ID: <20261005132742.324374-1-omermetekaya0@gmail.com> (raw)
The skb->len != 1 guard admits a 2-byte payload where config_status
at offset 2 lies one byte past skb->len.
Fix by guarding the nci_ver and config_status accesses with an explicit
skb->len >= 3 check, and restoring the original skb->len != 1 condition
around nci_req_complete() so the NCI 2.x reset request stays pending
until CORE_RESET_NTF arrives.
Fixes: bcd684aace34 ("net/nfc/nci: Support NCI 2.x initial sequence")
Signed-off-by: Ömer Mete Kaya <omermetekaya0@gmail.com>
---
Changes in v2:
- Preserve the original skb->len != 1 condition around
nci_req_complete() so the NCI 2.x reset request stays
pending until CORE_RESET_NTF arrives (reported by sashiko).
- Fix NCI version labels in comment (NCI 1.x = 3-byte RSP,
NCI 2.x = 1-byte RSP + NTF).
net/nfc/nci/rsp.c | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/net/nfc/nci/rsp.c b/net/nfc/nci/rsp.c
index e20df7fa0829..8226d09c99a5 100644
--- a/net/nfc/nci/rsp.c
+++ b/net/nfc/nci/rsp.c
@@ -32,22 +32,15 @@ static void nci_core_reset_rsp_packet(struct nci_dev *ndev,
pr_debug("status 0x%x\n", rsp->status);
- /* NCI 2.x reset response carries nci_ver and config_status;
- * a 1-byte response is the NCI 1.x status-only form.
- * Require at least 3 bytes before reading those fields.
- */
- if (skb->len == 1) {
- nci_req_complete(ndev, rsp->status);
- return;
- }
-
+ /* NCI 1.x: 3-byte RSP; NCI 2.x: 1-byte RSP, request completed by NTF. */
if (skb->len >= 3 && rsp->status == NCI_STATUS_OK) {
ndev->nci_ver = rsp->nci_ver;
pr_debug("nci_ver 0x%x, config_status 0x%x\n",
rsp->nci_ver, rsp->config_status);
}
- nci_req_complete(ndev, rsp->status);
+ if (skb->len != 1)
+ nci_req_complete(ndev, rsp->status);
}
static u8 nci_core_init_rsp_packet_v1(struct nci_dev *ndev,
--
2.55.0
next reply other threads:[~2026-10-05 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:26 Ömer Mete Kaya [this message]
2026-10-05 13:33 ` [PATCH net v2] nfc: nci: fix out-of-bounds read in nci_core_reset_rsp_packet() 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=20261005132742.324374-1-omermetekaya0@gmail.com \
--to=omermetekaya0@gmail.com \
--cc=davem@davemloft.net \
--cc=david@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 \
/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