From: Simon Horman <horms@kernel.org>
To: "Lekë Hapçiu" <snowwlake@icloud.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, "Lekë Hapçiu" <framemain@outlook.com>
Subject: Re: [PATCH net v3 2/4] nfc: llcp: fix TLV parsing in parse_gb_tlv and parse_connection_tlv
Date: Fri, 17 Apr 2026 17:04:38 +0100 [thread overview]
Message-ID: <20260417160438.GH31784@horms.kernel.org> (raw)
In-Reply-To: <20260414233534.55973-3-snowwlake@icloud.com>
On Wed, Apr 15, 2026 at 01:35:31AM +0200, Lekë Hapçiu wrote:
> From: Lekë Hapçiu <framemain@outlook.com>
>
> nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() walk TLV
> arrays whose length and content come from a peer-supplied frame. The
> parsing loop has three weaknesses:
>
> 1. `offset` is declared u8 while `tlv_array_len` is u16. In
> parse_connection_tlv() the TLV array can reach ~2173 bytes (MIUX
> up to 0x7FF), so 128 zero-length TLVs wrap `offset` back to 0 and
> the loop never terminates while `tlv` advances past the buffer.
>
> 2. The guard `offset < tlv_array_len` only proves one byte is
> available, but the body reads tlv[0] (type) and tlv[1] (length).
> When one byte remains, tlv[1] is out of bounds.
>
> 3. `length` is read from peer data and used to advance `tlv` without
> being checked against the remaining array space. A crafted length
> walks `tlv` past the buffer; the next iteration reads tlv[0]/tlv[1]
> from adjacent memory.
>
> The llcp_tlv8() and llcp_tlv16() accessors additionally read tlv[2]
> and tlv[2..3]; a zero-length TLV makes those reads out of bounds.
>
> Fix: promote `offset` to u16; add two per-iteration guards, one for
> the TLV header and one for the TLV value; require length >= 1 for all
> TLVs before the type dispatch and length >= 2 for the llcp_tlv16()
> accessors (MIUX, WKS). Return -EINVAL on malformed input.
>
> Reached on ATR_RES (parse_gb_tlv) and on CONNECT/CC PDUs before a
> connection is established (parse_connection_tlv). Both are
> triggerable from any NFC peer within ~4 cm, without authentication.
As per my comment on patch 1/4, I don't understand the relationship
between the last sentence above and this patch.
>
> Reported-by: Simon Horman <horms@kernel.org>
> Fixes: d646960f7986 ("NFC: Add LLCP sockets")
I think the hash but not the subject is correct in the fixes line.
IOW, I think this should be:
Fixes: d646960f7986 ("NFC: Initial LLCP support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Lekë Hapçiu <framemain@outlook.com>
Otherwise, looks good to me.
While looking over this I noticed that nfc_llcp_connect_sn() seems
to have the same kind of problem. You may wish to address that as
a follow-up.
...
prev parent reply other threads:[~2026-04-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 23:35 [PATCH net v3 2/4] nfc: llcp: fix TLV parsing in parse_gb_tlv and parse_connection_tlv Lekë Hapçiu
2026-04-17 16:04 ` 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=20260417160438.GH31784@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=framemain@outlook.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=snowwlake@icloud.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