| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAE=gft6H29BM5k5q=t-eQ_2LT1GORqqhQReVQZ7VCKn7=Oz=Yg@mail.gmail.com>
Date: Tue, 8 Jan 2019 10:30:04 -0800
From: Evan Green <evgreen@...omium.org>
To: Lina Iyer <ilina@...eaurora.org>
Cc: Stephen Boyd <swboyd@...omium.org>,
Andy Gross <andy.gross@...aro.org>,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
"Raju P.L.S.S.S.N" <rplsssn@...eaurora.org>,
Matthias Kaehlcke <mka@...omium.org>
Subject: Re: [PATCH] soc: qcom: rpmh: Avoid accessing freed memory from batch API
On Tue, Jan 8, 2019 at 9:49 AM Lina Iyer <ilina@...eaurora.org> wrote:
>
> On Thu, Jan 03 2019 at 10:47 -0700, Stephen Boyd wrote:
> >Using the batch API from the interconnect driver sometimes leads to a
> >KASAN error due to an access to freed memory. This is easier to trigger
> >with threadirqs on the kernel commandline.
> >
> > BUG: KASAN: use-after-free in rpmh_tx_done+0x114/0x12c
> > Read of size 1 at addr fffffff51414ad84 by task irq/110-apps_rs/57
> >
> > CPU: 0 PID: 57 Comm: irq/110-apps_rs Tainted: G W 4.19.10 #72
> > Call trace:
> > dump_backtrace+0x0/0x2f8
> > show_stack+0x20/0x2c
> > __dump_stack+0x20/0x28
> > dump_stack+0xcc/0x10c
> > print_address_description+0x74/0x240
> > kasan_report+0x250/0x26c
> > __asan_report_load1_noabort+0x20/0x2c
> > rpmh_tx_done+0x114/0x12c
> > tcs_tx_done+0x450/0x768
> > irq_forced_thread_fn+0x58/0x9c
> > irq_thread+0x120/0x1dc
> > kthread+0x248/0x260
> > ret_from_fork+0x10/0x18
> >
> > Allocated by task 385:
> > kasan_kmalloc+0xac/0x148
> > __kmalloc+0x170/0x1e4
> > rpmh_write_batch+0x174/0x540
> > qcom_icc_set+0x8dc/0x9ac
> > icc_set+0x288/0x2e8
> > a6xx_gmu_stop+0x320/0x3c0
> > a6xx_pm_suspend+0x108/0x124
> > adreno_suspend+0x50/0x60
> > pm_generic_runtime_suspend+0x60/0x78
> > __rpm_callback+0x214/0x32c
> > rpm_callback+0x54/0x184
> > rpm_suspend+0x3f8/0xa90
> > pm_runtime_work+0xb4/0x178
> > process_one_work+0x544/0xbc0
> > worker_thread+0x514/0x7d0
> > kthread+0x248/0x260
> > ret_from_fork+0x10/0x18
> >
> > Freed by task 385:
> > __kasan_slab_free+0x12c/0x1e0
> > kasan_slab_free+0x10/0x1c
> > kfree+0x134/0x588
> > rpmh_write_batch+0x49c/0x540
> > qcom_icc_set+0x8dc/0x9ac
> > icc_set+0x288/0x2e8
> > a6xx_gmu_stop+0x320/0x3c0
> > a6xx_pm_suspend+0x108/0x124
> > adreno_suspend+0x50/0x60
> > cr50_spi spi5.0: SPI transfer timed out
> > pm_generic_runtime_suspend+0x60/0x78
> > __rpm_callback+0x214/0x32c
> > rpm_callback+0x54/0x184
> > rpm_suspend+0x3f8/0xa90
> > pm_runtime_work+0xb4/0x178
> > process_one_work+0x544/0xbc0
> > worker_thread+0x514/0x7d0
> > kthread+0x248/0x260
> > ret_from_fork+0x10/0x18
> >
> > The buggy address belongs to the object at fffffff51414ac80
> > which belongs to the cache kmalloc-512 of size 512
> > The buggy address is located 260 bytes inside of
> > 512-byte region [fffffff51414ac80, fffffff51414ae80)
> > The buggy address belongs to the page:
> > page:ffffffbfd4505200 count:1 mapcount:0 mapping:fffffff51e00c680 index:0x0 compound_mapcount: 0
> > flags: 0x4000000000008100(slab|head)
> > raw: 4000000000008100 ffffffbfd4529008 ffffffbfd44f9208 fffffff51e00c680
> > raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000
> > page dumped because: kasan: bad access detected
> >
> > Memory state around the buggy address:
> > fffffff51414ac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> > fffffff51414ad00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> > >fffffff51414ad80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> > ^
> > fffffff51414ae00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> > fffffff51414ae80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> >
> >The batch API sets the same completion for each rpmh message that's sent
> >and then loops through all the messages and waits for that single
> >completion declared on the stack to be completed before returning from
> >the function and freeing the message structures. Unfortunately, some
> >messages may still be in process and 'stuck' in the TCS. At some later
> >point, the tcs_tx_done() interrupt will run and try to process messages
> >that have already been freed at the end of rpmh_write_batch(). This will
> >in turn access the 'needs_free' member of the rpmh_request structure and
> >cause KASAN to complain.
> >
> Raju and I were discussing this solution and we think the issue may be
> because of a race condition between the thread calling the completion
> and the thread waiting for completion. Completion releases the waiting
> thread and then we try to read rpm_msg->needs_free after that. But, if
> we could read in the rpm_msg->needs_free before calling completion, we
> would not see the problem. How about this instead?
>
> diff --git a/drivers/soc/qcom/rpmh.c b/drivers/soc/qcom/rpmh.c
> index c7beb6841289..0303a2971d4a 100644
> --- a/drivers/soc/qcom/rpmh.c
> +++ b/drivers/soc/qcom/rpmh.c
> @@ -80,6 +80,7 @@ void rpmh_tx_done(const struct tcs_request *msg, int r)
> struct rpmh_request *rpm_msg = container_of(msg, struct rpmh_request,
> msg);
> struct completion *compl = rpm_msg->completion;
> + bool free = rpm_msg->needs_free;
>
> rpm_msg->err = r;
>
> @@ -94,7 +95,7 @@ void rpmh_tx_done(const struct tcs_request *msg, int r)
> complete(compl);
>
> exit:
> - if (rpm_msg->needs_free)
> + if (free)
> kfree(rpm_msg);
> }
>
Hi Lina,
I think that's a worthy fix, too, and is needed to solve the issue you describe.
But I think Stephen's fix is still needed. In the rpmh_write_batch
scenario, we queue N things into rpmh, but set the same completion for
all of them. If only the first one completes but not the others, then
the loop in rpmh_write_batch will call wait_for_completion_timeout N
times on the same completion, and then goes on to free all N requests,
even though only the first one is actually done and out of the system
(well, almost out of the system, with the bug you noticed above).
We considered having just one completion on the last transfer, but
then if there's an error part way through you have no way of waiting
on the transfers that did get submitted. So I think N completions are
needed.
-Evan
Powered by blists - more mailing lists