From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Zhigulin <Pavel.Zhigulin@kaspersky.com>
Cc: manishc@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
Yuval.Mintz@qlogic.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH net] net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()
Date: Tue, 18 Nov 2025 10:20:05 +0000 [thread overview]
Message-ID: <176346120591.4081375.10043652831381384268.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113112757.4166625-1-Pavel.Zhigulin@kaspersky.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 13 Nov 2025 14:27:56 +0300 you wrote:
> The loops in 'qede_tpa_cont()' and 'qede_tpa_end()', iterate
> over 'cqe->len_list[]' using only a zero-length terminator as
> the stopping condition. If the terminator was missing or
> malformed, the loop could run past the end of the fixed-size array.
>
> Add an explicit bound check using ARRAY_SIZE() in both loops to prevent
> a potential out-of-bounds access.
>
> [...]
Here is the summary with links:
- [net] net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()
https://git.kernel.org/netdev/net/c/896f1a2493b5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-18 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 11:27 [PATCH net] net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() Pavel Zhigulin
2025-11-18 10:20 ` 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=176346120591.4081375.10043652831381384268.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Pavel.Zhigulin@kaspersky.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=manishc@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox