From: Simon Horman <horms@kernel.org>
To: Aamir Ahmed <elb12345@hotmail.co.uk>
Cc: 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>,
Christophe Ricard <christophe.ricard@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
oe-linux-nfc@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] nfc: nci: validate CORE_CONN_CREATE response length before reading fields
Date: Fri, 11 Sep 2026 13:27:50 +0100 [thread overview]
Message-ID: <20260911122750.GF48209@horms.kernel.org> (raw)
In-Reply-To: <AS8P251MB00015EC8F8C2D4D9B536F94DC8B22@AS8P251MB0001.EURP251.PROD.OUTLOOK.COM>
On Mon, Sep 07, 2026 at 06:28:55AM +0000, Aamir Ahmed wrote:
> nci_core_conn_create_rsp_packet() casts skb->data to struct
> nci_core_conn_create_rsp and accesses its conn_id,
> max_ctrl_pkt_payload_len, and credits_cnt fields (offsets 1-3) when
> the status byte is NCI_STATUS_OK. However, the NCI transport layer
> (nci_valid_size) only guarantees that the payload contains at least
> one byte. A malformed response with plen=1 and status=0 passes this
> check, and the handler then reads three bytes past the valid payload,
> using uninitialised slab data to populate the connection info that is
> later used for NFC data exchange.
>
> This can be triggered from userspace via the virtual_ncidev interface
> by injecting a short CORE_CONN_CREATE_RSP frame.
>
> Add a length check for the full response structure before accessing
> any field beyond the status byte.
>
> Fixes: 736bb9577407 ("NFC: nci: Support logical connections management")
> Cc: stable@vger.kernel.org
> Signed-off-by: Aamir Ahmed <elb12345@hotmail.co.uk>
This patch looks good to me but as noted collectively by Greg and Paolo
elsewhere:
1. Please include an Assisted-by tag
2. Please keep the number of patches in-flight to 15 or less
When you repost feel free to include:
Reviewed-by: Simon Horman <horms@kernel.org>
--
pw-bot: changes-requested
prev parent reply other threads:[~2026-09-11 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:28 Aamir Ahmed
2026-09-11 12:27 ` Simon Horman [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=20260911122750.GF48209@horms.kernel.org \
--to=horms@kernel.org \
--cc=christophe.ricard@gmail.com \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=edumazet@google.com \
--cc=elb12345@hotmail.co.uk \
--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
all inboxes | Powered by JetHome®