mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "libaokun (A)" <libaokun1@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>,
	<damien.lemoal@opensource.wdc.com>, <axboe@kernel.dk>,
	<tj@kernel.org>, <linux-ide@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <yebin10@huawei.com>, <yukuai3@huawei.com>,
	<stable@vger.kernel.org>, Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH -next V5 1/2] sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
Date: Sat, 27 Nov 2021 09:35:40 +0800	[thread overview]
Message-ID: <87fba93f-3813-87e2-9746-55c2393bde95@huawei.com> (raw)
In-Reply-To: <f8acc1f0-62d1-3c80-840f-1e38e21ad3c9@gmail.com>

在 2021/11/27 3:43, Sergei Shtylyov 写道:
> On 11/26/21 5:03 AM, Baokun Li wrote:
>
>> When the `rmmod sata_fsl.ko` command is executed in the PPC64 GNU/Linux,
>> a bug is reported:
>>   ==================================================================
>>   BUG: Unable to handle kernel data access on read at 0x80000800805b502c
>>   Oops: Kernel access of bad area, sig: 11 [#1]
>>   NIP [c0000000000388a4] .ioread32+0x4/0x20
>>   LR [80000000000c6034] .sata_fsl_port_stop+0x44/0xe0 [sata_fsl]
>>   Call Trace:
>>    .free_irq+0x1c/0x4e0 (unreliable)
>>    .ata_host_stop+0x74/0xd0 [libata]
>>    .release_nodes+0x330/0x3f0
>>    .device_release_driver_internal+0x178/0x2c0
>>    .driver_detach+0x64/0xd0
>>    .bus_remove_driver+0x70/0xf0
>>    .driver_unregister+0x38/0x80
>>    .platform_driver_unregister+0x14/0x30
>>    .fsl_sata_driver_exit+0x18/0xa20 [sata_fsl]
>>    .__se_sys_delete_module+0x1ec/0x2d0
>>    .system_call_exception+0xfc/0x1f0
>>    system_call_common+0xf8/0x200
>>   ==================================================================
>>
>> The triggering of the BUG is shown in the following stack:
>>
>> driver_detach
>>    device_release_driver_internal
>>      __device_release_driver
>>        drv->remove(dev) --> platform_drv_remove/platform_remove
>>          drv->remove(dev) --> sata_fsl_remove
>>            iounmap(host_priv->hcr_base);			<---- unmap
>>            kfree(host_priv);                             <---- free
>>        devres_release_all
>>          release_nodes
>>            dr->node.release(dev, dr->data) --> ata_host_stop
>>              ap->ops->port_stop(ap) --> sata_fsl_port_stop
>>                  ioread32(hcr_base + HCONTROL)           <---- UAF
>>              host->ops->host_stop(host)
>>
>> The iounmap(host_priv->hcr_base) and kfree(host_priv) functions should
>> not be executed in drv->remove. These functions should be executed in
>> host_stop after port_stop. Therefore, we move these functions to the
>> new function sata_fsl_host_stop and bind the new function to host_stop.
>>
>> Fixes: faf0b2e5afe7 ("drivers/ata: add support to Freescale 3.0Gbps SATA Controller")
>> Cc: stable@vger.kernel.org
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> Reviewed-by: Sergei Shtylyov <sergei.shtylyov@gmail.com>
>
> MBR, Sergei
> .

Thank you for your review.

-- 
With Best Regards,
Baokun Li
.


  reply	other threads:[~2021-11-27  1:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26  2:03 [PATCH -next V5 0/2] fix two bugs when trying " Baokun Li
2021-11-26  1:56 ` Damien Le Moal
2021-11-26 19:27   ` Sergei Shtylyov
2021-11-26  2:03 ` [PATCH -next V5 1/2] sata_fsl: fix UAF in sata_fsl_port_stop when " Baokun Li
2021-11-26 19:43   ` Sergei Shtylyov
2021-11-27  1:35     ` libaokun (A) [this message]
2021-11-26  2:03 ` [PATCH -next V5 2/2] sata_fsl: fix warning in remove_proc_entry " Baokun Li
2021-11-26 19:44   ` Sergei Shtylyov
2021-11-27  1:36     ` libaokun (A)
2021-11-29 11:38 ` [PATCH -next V5 0/2] fix two bugs when trying " Damien Le Moal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fba93f-3813-87e2-9746-55c2393bde95@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hulkci@huawei.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergei.shtylyov@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=yebin10@huawei.com \
    --cc=yukuai3@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®