From: Vinod Koul <vkoul@kernel.org>
To: neil.armstrong@linaro.org, mani@kernel.org, krzk@kernel.org,
peter.griffin@linaro.org, alim.akhtar@samsung.com,
pritam.sutar@samsung.com, andre.draszik@linaro.org,
kernel@lvkasz.us, pengpeng@iscas.ac.cn, kishon@kernel.org,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Selvarasu Ganesan <selvarasu.g@samsung.com>
Cc: jh0801.jung@samsung.com, h10.kim@samsung.com,
dh10.jung@samsung.com, akash.m5@samsung.com,
hongpooh.kim@samsung.com, eomji.oh@samsung.com,
shijie.cai@samsung.com, muhammed.ali@samsung.com,
thiagu.r@samsung.com, stable@vger.kernel.org
Subject: Re: [PATCH v3] phy: exynos5-usbdrd: Use dynamic phy_cfg size to prevent OOB access
Date: Thu, 12 Nov 2026 16:56:55 +0530 [thread overview]
Message-ID: <179448281584.507383.1286765834477602323.b4-ty@kernel.org> (raw)
In-Reply-To: <20261020063559.3530901-1-selvarasu.g@samsung.com>
On Tue, 20 Oct 2026 12:05:59 +0530, Selvarasu Ganesan wrote:
> The probe loop currently iterates using EXYNOS5_DRDPHYS_NUM (2),
> creating both UTMI and PIPE3 PHY instances regardless of the SoC
> capability. Several SoCs (Exynos2200, Exynos7870, Exynos850, Exynos990,
> and ExynosAutoV920) provide phy_cfg arrays containing only a single
> element.
>
> On these SoCs, when the loop reaches index 1, the driver reads past the
> end of the rodata array, populating the second PHY instance with garbage
> data. Since the configuration structure contains critical function
> pointers (phy_isol, phy_init, set_refclk), any subsequent access to this
> PHY instance via exynos5_usbdrd_phy_xlate could result in a kernel oops.
>
> [...]
Applied, thanks!
[1/1] phy: exynos5-usbdrd: Use dynamic phy_cfg size to prevent OOB access
commit: ba6618a1e7c02f384069f7817133ff8cb5c793b8
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-11-12 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261020063617epcas5p4ba00854fcd38bf211c573629ee062621@epcas5p4.samsung.com>
2026-10-20 6:35 ` Selvarasu Ganesan
2026-11-01 10:42 ` Manivannan Sadhasivam
2026-11-12 11:26 ` 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=179448281584.507383.1286765834477602323.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=akash.m5@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=dh10.jung@samsung.com \
--cc=eomji.oh@samsung.com \
--cc=h10.kim@samsung.com \
--cc=hongpooh.kim@samsung.com \
--cc=jh0801.jung@samsung.com \
--cc=kernel@lvkasz.us \
--cc=kishon@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=muhammed.ali@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=pengpeng@iscas.ac.cn \
--cc=peter.griffin@linaro.org \
--cc=pritam.sutar@samsung.com \
--cc=selvarasu.g@samsung.com \
--cc=shijie.cai@samsung.com \
--cc=stable@vger.kernel.org \
--cc=thiagu.r@samsung.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
all inboxes | Powered by JetHome®