From: Wolfram Sang <wsa@the-dreams.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Erico Nunes <erico.nunes@datacom.ind.br>,
linux-i2c@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] i2c: dev: use after free in detach
Date: Sat, 28 May 2016 10:57:20 +0200 [thread overview]
Message-ID: <20160528085719.GA1625@katana> (raw)
In-Reply-To: <20160528050146.GC4107@mwanda>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Sat, May 28, 2016 at 08:01:46AM +0300, Dan Carpenter wrote:
> The call to return_i2c_dev() frees "i2c_dev" so there is a use after
> free when we call cdev_del(&i2c_dev->cdev).
>
> Fixes: d6760b14d4a1 ('i2c: dev: switch from register_chrdev to cdev API')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks! I'll revert the offending commit nonetheless because I still
want to understand first why it slipped through my test system. And then
we will try again with a better patch.
>
> diff --git a/drivers/i2c/i2c-dev.c b/drivers/i2c/i2c-dev.c
> index 2562a45..3bf4f0d 100644
> --- a/drivers/i2c/i2c-dev.c
> +++ b/drivers/i2c/i2c-dev.c
> @@ -592,9 +592,9 @@ static int i2cdev_detach_adapter(struct device *dev, void *dummy)
> if (!i2c_dev) /* attach_adapter must have failed */
> return 0;
>
> + cdev_del(&i2c_dev->cdev);
> return_i2c_dev(i2c_dev);
> device_destroy(i2c_dev_class, MKDEV(I2C_MAJOR, adap->nr));
> - cdev_del(&i2c_dev->cdev);
>
> pr_debug("i2c-dev: adapter [%s] unregistered\n", adap->name);
> return 0;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-28 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 5:01 [patch] i2c: dev: use after free in detach Dan Carpenter
2016-05-28 8:57 ` Wolfram Sang [this message]
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=20160528085719.GA1625@katana \
--to=wsa@the-dreams.de \
--cc=dan.carpenter@oracle.com \
--cc=erico.nunes@datacom.ind.br \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).