From: Fernando Fernandez Mancera <fmancera@suse.de>
To: luka.gejak@linux.dev, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, fmaurer@redhat.com, horms@kernel.org
Subject: Re: [PATCH net-next v4 1/2] net: hsr: require valid EOT supervision TLV
Date: Wed, 1 Apr 2026 16:47:04 +0200 [thread overview]
Message-ID: <2d94a1a6-e6c5-427c-b10f-63377cb10407@suse.de> (raw)
In-Reply-To: <20260401092324.52266-2-luka.gejak@linux.dev>
On 4/1/26 11:23 AM, luka.gejak@linux.dev wrote:
> From: Luka Gejak <luka.gejak@linux.dev>
>
> Supervision frames are only valid if terminated with a zero-length EOT
> TLV. The current check fails to reject non-EOT entries as the terminal
> TLV, potentially allowing malformed supervision traffic.
>
> Fix this by strictly requiring the terminal TLV to be HSR_TLV_EOT
> with a length of zero.
>
> Reviewed-by: Felix Maurer <fmaurer@redhat.com>
> Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
> ---
> net/hsr/hsr_forward.c | 41 ++++++++++++++++++++++-------------------
> 1 file changed, 22 insertions(+), 19 deletions(-)
>
> diff --git a/net/hsr/hsr_forward.c b/net/hsr/hsr_forward.c
> index 0aca859c88cb..17b705235c4a 100644
> --- a/net/hsr/hsr_forward.c
> +++ b/net/hsr/hsr_forward.c
> @@ -82,39 +82,42 @@ static bool is_supervision_frame(struct hsr_priv *hsr, struct sk_buff *skb)
> hsr_sup_tag->tlv.HSR_TLV_length != sizeof(struct hsr_sup_payload))
> return false;
>
> - /* Get next tlv */
> + /* Advance past the first TLV payload to reach next TLV header */
> total_length += hsr_sup_tag->tlv.HSR_TLV_length;
> - if (!pskb_may_pull(skb, total_length))
> + /* Linearize next TLV header before access */
> + if (!pskb_may_pull(skb, total_length + sizeof(struct hsr_sup_tlv)))
> return false;
> skb_pull(skb, total_length);
> hsr_sup_tlv = (struct hsr_sup_tlv *)skb->data;
> skb_push(skb, total_length);
>
> - /* if this is a redbox supervision frame we need to verify
> - * that more data is available
> + /* Walk through TLVs to find end-of-TLV marker, skipping any unknown
> + * extension TLVs to maintain forward compatibility.
> */
> - if (hsr_sup_tlv->HSR_TLV_type == PRP_TLV_REDBOX_MAC) {
> - /* tlv length must be a length of a mac address */
> - if (hsr_sup_tlv->HSR_TLV_length != sizeof(struct hsr_sup_payload))
> - return false;
> + for (;;) {
> + if (hsr_sup_tlv->HSR_TLV_type == HSR_TLV_EOT &&
> + hsr_sup_tlv->HSR_TLV_length == 0)
> + return true;
>
I do not follow this approach, why a loop? From IEC 62439-3, I do not
understand that supervision frames could have multiple
PRP_TLV_REDBOX_MAC TLVs. The current code handles the TLVs correctly.
Which makes me wonder, how are you testing this? Do you have some
hardware with HSR/PRP support that is sending these frames? If so, which
one? Are you testing this using a HSR/PRP environment with purely Linux
devices?
Thanks,
Fernando.
> - /* make sure another tlv follows */
> - total_length += sizeof(struct hsr_sup_tlv) + hsr_sup_tlv->HSR_TLV_length;
> - if (!pskb_may_pull(skb, total_length))
> + /* Validate known TLV types */
> + if (hsr_sup_tlv->HSR_TLV_type == PRP_TLV_REDBOX_MAC) {
> + if (hsr_sup_tlv->HSR_TLV_length !=
> + sizeof(struct hsr_sup_payload))
> + return false;
> + }
> +
> + /* Advance past current TLV: header + payload */
> + total_length += sizeof(struct hsr_sup_tlv) +
> + hsr_sup_tlv->HSR_TLV_length;
> + /* Linearize next TLV header before access */
> + if (!pskb_may_pull(skb,
> + total_length + sizeof(struct hsr_sup_tlv)))
> return false;
>
> - /* get next tlv */
> skb_pull(skb, total_length);
> hsr_sup_tlv = (struct hsr_sup_tlv *)skb->data;
> skb_push(skb, total_length);
> }
next prev parent reply other threads:[~2026-04-01 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 9:23 [PATCH net-next v4 0/2] net: hsr: strict supervision TLV validation luka.gejak
2026-04-01 9:23 ` [PATCH net-next v4 1/2] net: hsr: require valid EOT supervision TLV luka.gejak
2026-04-01 9:52 ` Fernando Fernandez Mancera
2026-04-01 11:06 ` Luka Gejak
2026-04-01 12:05 ` Fernando Fernandez Mancera
2026-04-01 13:31 ` Luka Gejak
2026-04-01 13:44 ` Fernando Fernandez Mancera
2026-04-01 14:19 ` Luka Gejak
2026-04-01 17:05 ` Luka Gejak
2026-04-01 23:30 ` Fernando Fernandez Mancera
2026-04-02 6:34 ` Luka Gejak
2026-04-01 14:47 ` Fernando Fernandez Mancera [this message]
2026-04-01 16:59 ` Luka Gejak
2026-04-01 23:53 ` Fernando Fernandez Mancera
2026-04-01 9:23 ` [PATCH net-next v4 2/2] net: hsr: reject unresolved interlink ifindex luka.gejak
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=2d94a1a6-e6c5-427c-b10f-63377cb10407@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=luka.gejak@linux.dev \
--cc=netdev@vger.kernel.org \
--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