From: patchwork-bot+netdevbpf@kernel.org
To: John Keeping <john@metanate.com>
Cc: netdev@vger.kernel.org, linux-rockchip@lists.infradead.org,
peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, david.wu@rock-chips.com,
ezequiel@vanguardiasur.com.ar,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup
Date: Thu, 16 Dec 2021 20:51:40 +0000 [thread overview]
Message-ID: <163968790071.17466.7200435085941937139.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211214191009.2454599-1-john@metanate.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 14 Dec 2021 19:10:09 +0000 you wrote:
> KASAN reports an out-of-bounds read in rk_gmac_setup on the line:
>
> while (ops->regs[i]) {
>
> This happens for most platforms since the regs flexible array member is
> empty, so the memory after the ops structure is being read here. It
> seems that mostly this happens to contain zero anyway, so we get lucky
> and everything still works.
>
> [...]
Here is the summary with links:
- net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup
https://git.kernel.org/netdev/net/c/0546b224cc77
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:[~2021-12-16 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 19:10 [PATCH] net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup John Keeping
2021-12-16 20:51 ` 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=163968790071.17466.7200435085941937139.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=joabreu@synopsys.com \
--cc=john@metanate.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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