public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Luke Howard <lukeh@padl.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: validate source trunk against lags_len
Date: Thu, 31 Jul 2025 10:23:24 +0200	[thread overview]
Message-ID: <4d88953a-8ffd-46a6-b1ab-16d9587b6e90@linux.intel.com> (raw)
In-Reply-To: <DEC3889D-5C54-4648-B09F-44C7C69A1F91@padl.com>

On 2025-07-31 7:35 AM, Luke Howard wrote:
> A DSA frame with an invalid source trunk ID could cause an out-of-bounds read
> access of dst->lags.
> 
> This patch adds a check to dsa_lag_by_id() to validate the LAG ID is not zero,

checkpatch is saying this line is not wrapped at 75 columns

> and is less than or equal to dst->lags_len. (The LAG ID is derived by adding
> one to the source trunk ID.)
> 
> Note: this is in the fast path for any frames within a trunk.
> 
> Signed-off-by: Luke Howard <lukeh@padl.com>

Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>

Thanks,
Dawid

> ---
>   include/net/dsa.h | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/include/net/dsa.h b/include/net/dsa.h
> index 2e148823c366c..67672c5ff22e5 100644
> --- a/include/net/dsa.h
> +++ b/include/net/dsa.h
> @@ -180,6 +180,9 @@ struct dsa_switch_tree {
>   static inline struct dsa_lag *dsa_lag_by_id(struct dsa_switch_tree *dst,
>   					    unsigned int id)
>   {
> +	if (unlikely(id == 0 || id > dst->lags_len))
> +		return NULL;
> +
>   	/* DSA LAG IDs are one-based, dst->lags is zero-based */
>   	return dst->lags[id - 1];
>   }


  reply	other threads:[~2025-07-31  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31  5:35 [PATCH net] net: dsa: validate source trunk against lags_len Luke Howard
2025-07-31  8:23 ` Dawid Osuchowski [this message]
2025-07-31  9:07 ` Vladimir Oltean
2025-07-31  9:55   ` Luke Howard
2025-07-31 11:37     ` Vladimir Oltean
     [not found]       ` <C867697B-7F5B-4500-8098-9C44630D7930@padl.com>
     [not found]         ` <CAD3ieB36VnKAQPXUGbnRdWYFThf-VfLkhZTRfb9=ddndZEW3=A@mail.gmail.com>
2025-08-05  7:42           ` Vladimir Oltean
2025-08-05 11:52             ` Andrew Lunn
2025-08-06  1:28               ` Luke Howard
2025-07-31  9:56 ` [PATCH v2 net-next] " Luke Howard
2025-07-31 11:44   ` Vladimir Oltean
2025-07-31 13:07   ` Andrew Lunn

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=4d88953a-8ffd-46a6-b1ab-16d9587b6e90@linux.intel.com \
    --to=dawid.osuchowski@linux.intel.com \
    --cc=lukeh@padl.com \
    --cc=netdev@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