All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gwangun Jung <exsociety@gmail.com>
Cc: pabeni@redhat.com, jhs@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v3] net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg
Date: Fri, 14 Apr 2023 10:00:17 +0000	[thread overview]
Message-ID: <168146641747.17210.6250104828316736381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZDfbCsDa6oLKzsed@pr0lnx>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu, 13 Apr 2023 19:35:54 +0900 you wrote:
> If the TCA_QFQ_LMAX value is not offered through nlattr, lmax is determined by the MTU value of the network device.
> The MTU of the loopback device can be set up to 2^31-1.
> As a result, it is possible to have an lmax value that exceeds QFQ_MIN_LMAX.
> 
> Due to the invalid lmax value, an index is generated that exceeds the QFQ_MAX_INDEX(=24) value, causing out-of-bounds read/write errors.
> 
> The following reports a oob access:
> 
> [...]

Here is the summary with links:
  - [net,v3] net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg
    https://git.kernel.org/netdev/net/c/3037933448f6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-04-14 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 10:35 [PATCH net v3] net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg Gwangun Jung
2023-04-13 13:36 ` Jamal Hadi Salim
2023-04-14 10:00 ` patchwork-bot+netdevbpf [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=168146641747.17210.6250104828316736381.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=exsociety@gmail.com \
    --cc=jhs@mojatatu.com \
    --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 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.