From: Cong Wang <xiyou.wangcong@gmail.com>
To: Simon Horman <horms@kernel.org>
Cc: Maher Azzouzi <maherazz04@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
Ferenc Fejes <fejes@inf.elte.hu>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net] net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing
Date: Fri, 25 Jul 2025 11:03:59 -0700 [thread overview]
Message-ID: <aIPHD7Ktk8Q2kyrL@pop-os.localdomain> (raw)
In-Reply-To: <20250723125521.GA2459@horms.kernel.org>
On Wed, Jul 23, 2025 at 01:55:21PM +0100, Simon Horman wrote:
> + Ferenc and Vladimir
>
> On Tue, Jul 22, 2025 at 04:51:21PM +0100, Maher Azzouzi wrote:
> > From: MaherAzzouzi <maherazz04@gmail.com>
>
> nit: space between your names please
>
> >
> > TCA_MQPRIO_TC_ENTRY_INDEX is validated using
> > NLA_POLICY_MAX(NLA_U32, TC_QOPT_MAX_QUEUE), which allows the value
> > TC_QOPT_MAX_QUEUE (16). This leads to a 4-byte out-of-bounds stack write in
> > the fp[] array, which only has room for 16 elements (0–15).
> >
> > Fix this by changing the policy to allow only up to TC_QOPT_MAX_QUEUE - 1.
> >
> > Fixes: f62af20bed2d ("net/sched: mqprio: allow per-TC user input of FP adminStatus")
> > Reported-by: Maher Azzouzi <maherazz04@gmail.com>
>
> I don't think there is any need to include a Reported-by tag if
> you are also the patch author.
+1
>
> > Signed-off-by: Maher Azzouzi <maherazz04@gmail.com>
>
> I agree with your analysis and that this is a good fix.
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Reviewed-by: Cong Wang <xiyou.wangcong@gmail.com>
Thanks for the patch.
prev parent reply other threads:[~2025-07-25 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 15:51 [PATCH net] net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing Maher Azzouzi
2025-07-23 12:55 ` Simon Horman
[not found] ` <CAFQ-Uc_qYu--YG4LNVOB=UQeUGyuQ9fSPT=e52HwHu-j3kjQtQ@mail.gmail.com>
2025-07-23 14:31 ` Vladimir Oltean
2025-07-23 14:41 ` Vladimir Oltean
2025-07-25 18:03 ` Cong Wang [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=aIPHD7Ktk8Q2kyrL@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fejes@inf.elte.hu \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maherazz04@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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