[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190717042655.jmiblv5mhg55s7la@vireshk-i7>
Date: Wed, 17 Jul 2019 09:56:55 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Wen Yang <wen.yang99@....com.cn>
Cc: rjw@...ysocki.net, linuxppc-dev@...ts.ozlabs.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
xue.zhihong@....com.cn, wang.yi59@....com.cn,
cheng.shengyu@....com.cn, Michael Ellerman <mpe@...erman.id.au>
Subject: Re: [PATCH v7] cpufreq/pasemi: fix an use-after-free in
pas_cpufreq_cpu_init()
On 17-07-19, 11:55, Wen Yang wrote:
> The cpu variable is still being used in the of_get_property() call
> after the of_node_put() call, which may result in use-after-free.
>
> Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak")
> Signed-off-by: Wen Yang <wen.yang99@....com.cn>
> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>
> Cc: Viresh Kumar <viresh.kumar@...aro.org>
> Cc: Michael Ellerman <mpe@...erman.id.au>
> Cc: linuxppc-dev@...ts.ozlabs.org
> Cc: linux-pm@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> ---
> v7: adapt to commit ("cpufreq: Make cpufreq_generic_init() return void")
> v6: keep the blank line and fix warning: label 'out_unmap_sdcpwr' defined but not used.
> v5: put together the code to get, use, and release cpu device_node.
> v4: restore the blank line.
> v3: fix a leaked reference.
> v2: clean up the code according to the advice of viresh.
>
> drivers/cpufreq/pasemi-cpufreq.c | 23 +++++++++--------------
> 1 file changed, 9 insertions(+), 14 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
viresh
Powered by blists - more mailing lists