From: Vinod Koul <vkoul@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Mikhail Kobuk <m.kobuk@ispras.ru>
Cc: "Kishon Vijay Abraham I" <kishon@kernel.org>,
"Marek Behún" <kabel@kernel.org>, "Pali Rohár" <pali@kernel.org>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org,
"Alexey Khoroshilov" <khoroshilov@ispras.ru>
Subject: Re: [PATCH 1/2] phy: marvell: a3700-comphy: Fix out of bounds read
Date: Fri, 05 Apr 2024 22:38:50 +0530 [thread overview]
Message-ID: <171233693092.304466.7167467366245404657.b4-ty@kernel.org> (raw)
In-Reply-To: <20240321164734.49273-1-m.kobuk@ispras.ru>
On Thu, 21 Mar 2024 19:47:30 +0300, Mikhail Kobuk wrote:
> There is an out of bounds read access of 'gbe_phy_init_fix[fix_idx].addr'
> every iteration after 'fix_idx' reaches 'ARRAY_SIZE(gbe_phy_init_fix)'.
>
> Make sure 'gbe_phy_init[addr]' is used when all elements of
> 'gbe_phy_init_fix' array are handled.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> [...]
Applied, thanks!
[1/2] phy: marvell: a3700-comphy: Fix out of bounds read
commit: e4308bc22b9d46cf33165c9dfaeebcf29cd56f04
[2/2] phy: marvell: a3700-comphy: Fix hardcoded array size
commit: 627207703b73615653eea5ab7a841d5b478d961e
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-04-05 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:47 Mikhail Kobuk
2024-03-21 16:47 ` [PATCH 2/2] phy: marvell: a3700-comphy: Fix hardcoded array size Mikhail Kobuk
2024-03-22 7:26 ` Miquel Raynal
2024-03-22 7:25 ` [PATCH 1/2] phy: marvell: a3700-comphy: Fix out of bounds read Miquel Raynal
2024-04-05 17:08 ` Vinod Koul [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=171233693092.304466.7167467366245404657.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=kabel@kernel.org \
--cc=khoroshilov@ispras.ru \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lvc-project@linuxtesting.org \
--cc=m.kobuk@ispras.ru \
--cc=miquel.raynal@bootlin.com \
--cc=pali@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
all inboxes | Powered by JetHome®