From: Frank Li <Frank.li@nxp.com>
To: Kaixin Wang <kxwang23@m.fudan.edu.cn>
Cc: miquel.raynal@bootlin.com, 21210240012@m.fudan.edu.cn,
21302010073@m.fudan.edu.cn, conor.culhane@silvaco.com,
alexandre.belloni@bootlin.com, linux-i3c@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition
Date: Wed, 11 Sep 2024 11:24:57 -0400 [thread overview]
Message-ID: <ZuG2SbsHEU5BU9mX@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20240911150135.839946-1-kxwang23@m.fudan.edu.cn>
On Wed, Sep 11, 2024 at 11:01:35PM +0800, Kaixin Wang wrote:
> In the svc_i3c_master_probe function, &master->hj_work is bound with
> svc_i3c_master_hj_work, &master->ibi_work is bound with
> svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work can start the
> hj_work, svc_i3c_master_irq_handler can start the ibi_work.
>
> If we remove the module which will call svc_i3c_master_remove to
> make cleanup, it will free master->base through i3c_master_unregister
> while the work mentioned above will be used. The sequence of operations
> that may lead to a UAF bug is as follows:
>
> CPU0 CPU1
>
> | svc_i3c_master_hj_work
> svc_i3c_master_remove |
> i3c_master_unregister(&master->base)|
> device_unregister(&master->dev) |
> device_release |
> //free master->base |
> | i3c_master_do_daa(&master->base)
> | //use master->base
>
> Fix it by ensuring that the work is canceled before proceeding with the
> cleanup in svc_i3c_master_remove.
>
> Signed-off-by: Kaixin Wang <kxwang23@m.fudan.edu.cn>
> ---
Please add fixes tag and cc stable.
Frank
> drivers/i3c/master/svc-i3c-master.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i3c/master/svc-i3c-master.c b/drivers/i3c/master/svc-i3c-master.c
> index 0a68fd1b81d4..e084ba648b4a 100644
> --- a/drivers/i3c/master/svc-i3c-master.c
> +++ b/drivers/i3c/master/svc-i3c-master.c
> @@ -1775,6 +1775,7 @@ static void svc_i3c_master_remove(struct platform_device *pdev)
> {
> struct svc_i3c_master *master = platform_get_drvdata(pdev);
>
> + cancel_work_sync(&master->hj_work);
> i3c_master_unregister(&master->base);
>
> pm_runtime_dont_use_autosuspend(&pdev->dev);
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-09-11 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:01 Kaixin Wang
2024-09-11 15:24 ` Frank Li [this message]
2024-09-12 6:57 ` Miquel Raynal
2024-09-12 16:54 ` Kaixin Wang
2024-09-12 16:52 ` Kaixin Wang
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=ZuG2SbsHEU5BU9mX@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=21210240012@m.fudan.edu.cn \
--cc=21302010073@m.fudan.edu.cn \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=kxwang23@m.fudan.edu.cn \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.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®