From: Greg KH <gregkh@linuxfoundation.org>
To: Guanghui Feng <guanghuifeng@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, baolin.wang@linux.alibaba.com
Subject: Re: [PATCH] uio: Fix use-after-free in uio_open
Date: Thu, 21 Dec 2023 09:08:54 +0100 [thread overview]
Message-ID: <2023122115-strewn-unsigned-b3e5@gregkh> (raw)
In-Reply-To: <1703132808-14322-1-git-send-email-guanghuifeng@linux.alibaba.com>
On Thu, Dec 21, 2023 at 12:26:48PM +0800, Guanghui Feng wrote:
> core-1 core-2
> -------------------------------------------------------------
> uio_unregister_device uio_open
> idev = idr_find()
> device_unregister(&idev->dev)
> put_device(&idev->dev)
> uio_device_release
> get_device(&idev->dev)
> kfree(idev)
> uio_free_minor(minor)
> uio_release
> put_device(&idev->dev)
> kfree(idev)
> -------------------------------------------------------------
>
> In the core-1 uio_unregister_device(), the device_unregister will kfree idev
> when the idev->dev kobject ref is one. But after core-1 device_unregister,
> put_device and before doing kfree, the core-2 may get_device. Then:
> 1. After core-1 kfree idev, the core-2 will do use-after-free for idev.
> 2. When core-2 do uio_release and put_device, the idev will be double freed.
>
> To address this issue, we can get idev atomic & inc idev reference with minor_lock.
Nit, can you wrap your lines at 72 columns?
Anyway, nice fix, how did you find this?
> Signed-off-by: Guanghui Feng <guanghuifeng@linux.alibaba.com>
What commit id does this fix?
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-21 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 4:26 [PATCH] uio: Fix use-after-free in uio_open Guanghui Feng
2023-12-21 8:08 ` Greg KH [this message]
2023-12-21 9:57 ` [PATCH v2] " Guanghui Feng
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=2023122115-strewn-unsigned-b3e5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=guanghuifeng@linux.alibaba.com \
--cc=linux-kernel@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