public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hyunwoo Kim <imv4bel@gmail.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dvb-core: Fix UAF due to refcount races at releasing
Date: Tue, 11 Oct 2022 09:06:33 +0200	[thread overview]
Message-ID: <87k056dekm.wl-tiwai@suse.de> (raw)
In-Reply-To: <87sfklgozd.wl-tiwai@suse.de>

On Wed, 21 Sep 2022 09:34:30 +0200,
Takashi Iwai wrote:
> 
> On Thu, 08 Sep 2022 15:27:54 +0200,
> Takashi Iwai wrote:
> > 
> > The dvb-core tries to sync the releases of opened files at
> > dvb_dmxdev_release() with two refcounts: dvbdev->users and
> > dvr_dvbdev->users.  A problem is present in those two syncs: when yet
> > another dvb_demux_open() is called during those sync waits,
> > dvb_demux_open() continues to process even if the device is being
> > closed.  This includes the increment of the former refcount, resulting
> > in the leftover refcount after the sync of the latter refcount at
> > dvb_dmxdev_release().  It ends up with use-after-free, since the
> > function believes that all usages were gone and releases the
> > resources.
> > 
> > This patch addresses the problem by adding the check of dmxdev->exit
> > flag at dvb_demux_open(), just like dvb_dvr_open() already does.  With
> > the exit flag check, the second call of dvb_demux_open() fails, hence
> > the further corruption can be avoided.
> > 
> > Also for avoiding the races of the dmxdev->exit flag reference, this
> > patch serializes the dmxdev->exit set up and the sync waits with the
> > dmxdev->mutex lock at dvb_dmxdev_release().  Without the mutex lock,
> > dvb_demux_open() (or dvb_dvr_open()) may run concurrently with
> > dvb_dmxdev_release(), which allows to skip the exit flag check and
> > continue the open process that is being closed.
> > 
> > Reported-by: Hyunwoo Kim <imv4bel@gmail.com>
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> 
> Any review on this?
> 
> FWIW, now CVE-2022-41218 is assigned for those bugs as a security
> issue.

A gentle ping again.

Or if any other fix for this security issue is already available,
please let me know.


thanks,

Takashi

> 
> 
> thanks,
> 
> Takashi
> 
> > ---
> >  drivers/media/dvb-core/dmxdev.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/media/dvb-core/dmxdev.c b/drivers/media/dvb-core/dmxdev.c
> > index f6ee678107d3..9ce5f010de3f 100644
> > --- a/drivers/media/dvb-core/dmxdev.c
> > +++ b/drivers/media/dvb-core/dmxdev.c
> > @@ -790,6 +790,11 @@ static int dvb_demux_open(struct inode *inode, struct file *file)
> >  	if (mutex_lock_interruptible(&dmxdev->mutex))
> >  		return -ERESTARTSYS;
> >  
> > +	if (dmxdev->exit) {
> > +		mutex_unlock(&dmxdev->mutex);
> > +		return -ENODEV;
> > +	}
> > +
> >  	for (i = 0; i < dmxdev->filternum; i++)
> >  		if (dmxdev->filter[i].state == DMXDEV_STATE_FREE)
> >  			break;
> > @@ -1448,7 +1453,10 @@ EXPORT_SYMBOL(dvb_dmxdev_init);
> >  
> >  void dvb_dmxdev_release(struct dmxdev *dmxdev)
> >  {
> > +	mutex_lock(&dmxdev->mutex);
> >  	dmxdev->exit = 1;
> > +	mutex_unlock(&dmxdev->mutex);
> > +
> >  	if (dmxdev->dvbdev->users > 1) {
> >  		wait_event(dmxdev->dvbdev->wait_queue,
> >  				dmxdev->dvbdev->users == 1);
> > -- 
> > 2.35.3
> > 

  reply	other threads:[~2022-10-11  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 13:27 [PATCH] media: dvb-core: Fix UAF due to refcount races at releasing Takashi Iwai
2022-09-21  7:34 ` Takashi Iwai
2022-10-11  7:06   ` Takashi Iwai [this message]
2022-11-16 11:08     ` Salvatore Bonaccorso
2022-11-16 13:19       ` Hyunwoo Kim

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=87k056dekm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=imv4bel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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