[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC=S1njm0ExE3DvWZQyPBm7LC8P_aJXX0xVY=fPuGBe1BKVmwg@mail.gmail.com>
Date: Fri, 18 Aug 2023 13:09:04 +0800
From: Fei Shao <fshao@...omium.org>
To: Yu-Che Cheng <giver@...omium.org>
Cc: James Lo <james.lo@...iatek.com>, Stephen Boyd <sboyd@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] spmi: mediatek: Fix UAF on device remove
Just to float this up. Any feedback on this?
On Tue, Jul 18, 2023 at 2:57 PM Fei Shao <fshao@...omium.org> wrote:
>
> On Mon, Jul 17, 2023 at 5:41 PM Yu-Che Cheng <giver@...omium.org> wrote:
> >
> > The pmif driver data that contains the clocks is allocated along with
> > spmi_controller.
> > On device remove, spmi_controller will be freed first, and then devres
> > , including the clocks, will be cleanup.
> > This leads to UAF because putting the clocks will access the clocks in
> > the pmif driver data, which is already freed along with spmi_controller.
> >
> > This can be reproduced by enabling DEBUG_TEST_DRIVER_REMOVE and
> > building the kernel with KASAN.
> >
> > Fix the UAF issue by using unmanaged clk_bulk_get() and putting the
> > clocks before freeing spmi_controller.
> >
> > Reported-by: Fei Shao <fshao@...omium.org>
> > Signed-off-by: Yu-Che Cheng <giver@...omium.org>
>
> Reviewed-by: Fei Shao <fshao@...omium.org>
> Tested-by: Fei Shao <fshao@...omium.org>
Powered by blists - more mailing lists