[PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
walter-zh.wu at mediatek.com
Tue Dec 1 06:17:02 EST 2020
On Tue, 2020-12-01 at 08:59 +0100, 'Dmitry Vyukov' via kasan-dev wrote:
> On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx at linutronix.de> wrote:
> > On Thu, Sep 24 2020 at 12:01, Walter Wu wrote:
> > > Syzbot reports many UAF issues for workqueue or timer, see  and .
> > > In some of these access/allocation happened in process_one_work(),
> > > we see the free stack is useless in KASAN report, it doesn't help
> > > programmers to solve UAF on workqueue. The same may stand for times.
> > >
> > > This patchset improves KASAN reports by making them to have workqueue
> > > queueing stack and timer stack information. It is useful for programmers
> > > to solve use-after-free or double-free memory issue.
> > >
> > > Generic KASAN also records the last two workqueue and timer stacks and
> > > prints them in KASAN report. It is only suitable for generic KASAN.
> Walter, did you mail v5?
> Checking statuses of KASAN issues and this seems to be not in linux-next.
Sorry for the delay in responding to this patch. I'm busy these few
months, so that suspend processing it.
Yes, I will send it next week. But v4 need to confirm the timer stack is
useful. I haven't found an example. Do you have some suggestion about
> > > https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22+process_one_work
> > > https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22%20expire_timers
> > How are these links useful for people who do not have a gurgle account?
> This is a public mailing list archive, so effectively the same way as
> lore links ;)
More information about the linux-arm-kernel