From: Hyunwoo Kim <imv4bel@gmail.com>
To: lkundrak@v3.sk, arnd@arndb.de, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, imv4bel@gmail.com
Subject: [PATCH] char: pcmcia: scr24x_cs: Fix use-after-free in scr24x_fops
Date: Thu, 15 Sep 2022 22:00:06 -0700 [thread overview]
Message-ID: <20220916050006.GA188273@ubuntu> (raw)
A race condition may occur if the user physically removes the
pcmcia device while calling open() for this char device node.
This is a race condition between the scr24x_open() function and
the scr24x_remove() function, which may eventually result in UAF.
So, add a mutex to the scr24x_open() and scr24x_remove() functions
to avoid race contidion of krefs.
Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
---
drivers/char/pcmcia/scr24x_cs.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/char/pcmcia/scr24x_cs.c b/drivers/char/pcmcia/scr24x_cs.c
index 1bdce08fae3d..319e8d79048e 100644
--- a/drivers/char/pcmcia/scr24x_cs.c
+++ b/drivers/char/pcmcia/scr24x_cs.c
@@ -76,8 +76,10 @@ static int scr24x_open(struct inode *inode, struct file *filp)
struct scr24x_dev *dev = container_of(inode->i_cdev,
struct scr24x_dev, c_dev);
+ mutex_lock(&dev->lock);
kref_get(&dev->refcnt);
filp->private_data = dev;
+ mutex_unlock(&dev->lock);
return stream_open(inode, filp);
}
@@ -298,9 +300,10 @@ static void scr24x_remove(struct pcmcia_device *link)
cdev_del(&dev->c_dev);
clear_bit(dev->devno, scr24x_minors);
dev->dev = NULL;
- mutex_unlock(&dev->lock);
kref_put(&dev->refcnt, scr24x_delete);
+
+ mutex_unlock(&dev->lock);
}
static const struct pcmcia_device_id scr24x_ids[] = {
--
2.25.1
next reply other threads:[~2022-09-16 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 5:00 Hyunwoo Kim [this message]
2022-09-16 6:59 ` [PATCH] char: pcmcia: scr24x_cs: Fix use-after-free in scr24x_fops Arnd Bergmann
2022-09-16 8:11 ` 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=20220916050006.GA188273@ubuntu \
--to=imv4bel@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
/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