From: Simon Horman <horms@kernel.org>
To: Doruk Tan Ozturk <doruk@0sec.ai>
Cc: david@ixit.cz, oe-linux-nfc@lists.linux.dev,
david.laight.linux@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] nfc: llcp: bound the connect_sn TLV walk to the skb
Date: Thu, 16 Jul 2026 11:07:21 +0100 [thread overview]
Message-ID: <20260716100721.GG95246@horms.kernel.org> (raw)
In-Reply-To: <20260709131229.44477-1-doruk@0sec.ai>
On Thu, Jul 09, 2026 at 03:12:29PM +0200, Doruk Tan Ozturk wrote:
> Commit 27256cdb290e ("nfc: llcp: bound SNL TLV parsing to the skb and
> add length checks") fixed the unbounded TLV walk in nfc_llcp_recv_snl(),
> and commit d8bd2dedbde5 ("nfc: llcp: fix OOB read and u8 offset wrap in
> TLV parsers") subsequently bounded nfc_llcp_parse_gb_tlv() and
> nfc_llcp_parse_connection_tlv(). One sibling parser sharing the same
> pattern remains unbounded: nfc_llcp_connect_sn().
>
> nfc_llcp_connect_sn() walks a TLV list, reading a two-byte header
> (type, length) followed by length bytes of value, without checking that
> the two header bytes or the declared length stay within the buffer. It
> returns a pointer to a service name of up to 255 bytes that may point
> past the end of the skb; it is subsequently consumed by memcmp() in
> nfc_llcp_sock_from_sn(). In addition tlv_array_len was computed as
> "skb->len - LLCP_HEADER_SIZE" in size_t, so a CONNECT/CC frame shorter
> than the LLCP header underflows to a huge length and the walk runs far
> past the buffer.
>
> nfc_llcp_connect_sn() is reachable from nfc_llcp_recv_connect() and
> nfc_llcp_recv_cc(), i.e. from received CONNECT and CC PDUs. A nearby
> NFC device can reach this without authentication; LLCP link activation
> happens automatically after NFC-DEP, and the nfc_llcp_rx_skb()
> dispatcher applies no minimum-length guard.
>
> Walk the TLV list by pointer, bounded by skb_tail_pointer(skb), and
> validate each declared length before use, matching the approach already
> used for nfc_llcp_recv_snl(). Starting the walk at
> &skb->data[LLCP_HEADER_SIZE] against the tail pointer also removes the
> size_t underflow for short frames.
>
> Found by 0sec automated security-research tooling (https://0sec.ai).
>
> Fixes: d646960f7986 ("NFC: Initial LLCP support")
> Cc: stable@vger.kernel.org
> Assisted-by: 0sec:claude-opus-4-8
> Signed-off-by: Doruk Tan Ozturk <doruk@0sec.ai>
> ---
> v2: drop the nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv()
> hunks - fixed independently by d8bd2dedbde5. This resend covers only
> the still-unbounded nfc_llcp_connect_sn().
> v1: https://lore.kernel.org/netdev/20260705113505 net/nfc/llcp_core.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-07-16 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 13:12 [PATCH net v2] nfc: llcp: bound the connect_sn TLV walk to the skb Doruk Tan Ozturk
2026-07-16 10:07 ` 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=20260716100721.GG95246@horms.kernel.org \
--to=horms@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=david@ixit.cz \
--cc=doruk@0sec.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.