[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6wvXoIZVm96JP/D@zn.tnic>
Date: Wed, 28 Dec 2022 12:58:22 +0100
From: Borislav Petkov <bp@...en8.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: andersson@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, tony.luck@...el.com,
quic_saipraka@...cinc.com, konrad.dybcio@...aro.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
james.morse@....com, mchehab@...nel.org, rric@...nel.org,
linux-edac@...r.kernel.org, quic_ppareek@...cinc.com,
luca.weiss@...rphone.com, ahalaney@...hat.com, steev@...i.org,
stable@...r.kernel.org
Subject: Re: [PATCH v5 03/17] EDAC/qcom: Do not pass llcc_driv_data as
edac_device_ctl_info's pvt_info
On Wed, Dec 28, 2022 at 02:10:14PM +0530, Manivannan Sadhasivam wrote:
> The memory for "llcc_driv_data" is allocated by the LLCC driver. But when
> it is passed as "pvt_info" to the EDAC core, it will get freed during the
> qcom_edac driver release. So when the qcom_edac driver gets probed again,
> it will try to use the freed data leading to the use-after-free bug.
>
> Fix this by not passing "llcc_driv_data" as pvt_info but rather reference
"Do not pass ..."
> it using the "platform_data" in the qcom_edac driver.
>
> Cc: <stable@...r.kernel.org> # 4.20
> Fixes: 27450653f1db ("drivers: edac: Add EDAC driver support for QCOM SoCs")
> Tested-by: Steev Klimaszewski <steev@...i.org> # Thinkpad X13s
> Tested-by: Andrew Halaney <ahalaney@...hat.com> # sa8540p-ride
> Reported-by: Steev Klimaszewski <steev@...i.org>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> ---
> drivers/edac/qcom_edac.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
with that:
Reviewed-by: Borislav Petkov (AMD) <bp@...en8.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists