From: Dan Carpenter <dan.carpenter@oracle.com>
To: Wolfgang Grandegger <wg@grandegger.com>,
Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Leon Romanovsky <leon@kernel.org>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: [PATCH net-next] can: sja1000: fix use after free in ems_pcmcia_add_card()
Date: Mon, 22 Nov 2021 10:56:14 +0300 [thread overview]
Message-ID: <20211122075614.GB6581@kili> (raw)
In the original code if ems_pcmcia_check_chan() returned false then
it called free_sja1000dev(dev) but did not set the error code or jump
to the clean up code. This frees "dev" and leads to a use after free.
I flipped the ems_pcmcia_check_chan() check around to make the error
handling more consistent and readable. That lets us pull the rest of
the code in one tab.
Fixes: fd734c6f25ae ("can/sja1000: add driver for EMS PCMCIA card")
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
---
drivers/net/can/sja1000/ems_pcmcia.c | 44 +++++++++++++++-------------
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/drivers/net/can/sja1000/ems_pcmcia.c b/drivers/net/can/sja1000/ems_pcmcia.c
index e21b169c14c0..271fe9444827 100644
--- a/drivers/net/can/sja1000/ems_pcmcia.c
+++ b/drivers/net/can/sja1000/ems_pcmcia.c
@@ -210,28 +210,30 @@ static int ems_pcmcia_add_card(struct pcmcia_device *pdev, unsigned long base)
(i * EMS_PCMCIA_CAN_CTRL_SIZE);
/* Check if channel is present */
- if (ems_pcmcia_check_chan(priv)) {
- priv->read_reg = ems_pcmcia_read_reg;
- priv->write_reg = ems_pcmcia_write_reg;
- priv->can.clock.freq = EMS_PCMCIA_CAN_CLOCK;
- priv->ocr = EMS_PCMCIA_OCR;
- priv->cdr = EMS_PCMCIA_CDR;
- priv->flags |= SJA1000_CUSTOM_IRQ_HANDLER;
-
- /* Register SJA1000 device */
- err = register_sja1000dev(dev);
- if (err) {
- free_sja1000dev(dev);
- goto failure_cleanup;
- }
-
- card->channels++;
-
- printk(KERN_INFO "%s: registered %s on channel "
- "#%d at 0x%p, irq %d\n", DRV_NAME, dev->name,
- i, priv->reg_base, dev->irq);
- } else
+ if (!ems_pcmcia_check_chan(priv)) {
+ err = -EINVAL;
free_sja1000dev(dev);
+ goto failure_cleanup;
+ }
+ priv->read_reg = ems_pcmcia_read_reg;
+ priv->write_reg = ems_pcmcia_write_reg;
+ priv->can.clock.freq = EMS_PCMCIA_CAN_CLOCK;
+ priv->ocr = EMS_PCMCIA_OCR;
+ priv->cdr = EMS_PCMCIA_CDR;
+ priv->flags |= SJA1000_CUSTOM_IRQ_HANDLER;
+
+ /* Register SJA1000 device */
+ err = register_sja1000dev(dev);
+ if (err) {
+ free_sja1000dev(dev);
+ goto failure_cleanup;
+ }
+
+ card->channels++;
+
+ printk(KERN_INFO "%s: registered %s on channel "
+ "#%d at 0x%p, irq %d\n", DRV_NAME, dev->name,
+ i, priv->reg_base, dev->irq);
}
err = request_irq(dev->irq, &ems_pcmcia_interrupt, IRQF_SHARED,
--
2.20.1
next reply other threads:[~2021-11-22 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 7:56 Dan Carpenter [this message]
2021-11-22 8:03 ` [PATCH net-next] can: sja1000: fix use after free in ems_pcmcia_add_card() Dan Carpenter
2021-11-23 20:42 ` Oliver Hartkopp
2021-11-24 6:56 ` Dan Carpenter
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=20211122075614.GB6581@kili \
--to=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/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).