From: Wolfram Sang <wsa@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: core: fix potential use-after-free on adapter removal
Date: Tue, 14 Jun 2022 21:45:42 +0200 [thread overview]
Message-ID: <YqjlZuFGl0dAUZyd@shikoro> (raw)
In-Reply-To: <a9dc272e4e06db661125b7b4c330821b532afc4d.1642209079.git.mirq-linux@rere.qmqm.pl>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Hi Michał,
I finally had a look at your patch...
> put_device(&adap->dev) might free the memory pointed to by `adap`,
> so we shouldn't read adap->owner after that.
>
> Fix by saving module pointer before calling put_device().
... and found a different approach for this problem from 2019:
http://patchwork.ozlabs.org/project/linux-i2c/patch/1577439272-10362-1-git-send-email-vulab@iscas.ac.cn/
I think this is also proper. I found other subsystems in the kernel
first putting the module, then the device. Do you see problems with the
above patch?
Thanks for looking into the issue!
Wolfram
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> ---
> drivers/i2c/i2c-core-base.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> index 2c59dd748a49..5d694f8ce9ef 100644
> --- a/drivers/i2c/i2c-core-base.c
> +++ b/drivers/i2c/i2c-core-base.c
> @@ -2464,11 +2464,14 @@ EXPORT_SYMBOL(i2c_get_adapter);
>
> void i2c_put_adapter(struct i2c_adapter *adap)
> {
> + struct module *owner;
> +
> if (!adap)
> return;
>
> + owner = adap->owner;
> put_device(&adap->dev);
> - module_put(adap->owner);
> + module_put(owner);
> }
> EXPORT_SYMBOL(i2c_put_adapter);
>
> --
> 2.30.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-14 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 1:12 [PATCH] i2c: core: fix potential use-after-free on adapter removal Michał Mirosław
2022-06-14 19:45 ` Wolfram Sang [this message]
2022-06-15 18:01 ` Michał Mirosław
2022-06-16 19:32 ` Wolfram Sang
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=YqjlZuFGl0dAUZyd@shikoro \
--to=wsa@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
/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