All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: re: firmware: fix possible use after free on name on asynchronous request
Date: Thu, 28 May 2015 09:02:27 +0000	[thread overview]
Message-ID: <20150528090227.GA13248@mwanda> (raw)

Hello Luis R. Rodriguez,

The patch f9692b2699bd: "firmware: fix possible use after free on
name on asynchronous request" from May 12, 2015, leads to the
following static checker warning:

	drivers/base/firmware_class.c:1311 request_firmware_nowait()
	warn: possible memory leak of 'fw_work'

drivers/base/firmware_class.c
  1296  int
  1297  request_firmware_nowait(
  1298          struct module *module, bool uevent,
  1299          const char *name, struct device *device, gfp_t gfp, void *context,
  1300          void (*cont)(const struct firmware *fw, void *context))
  1301  {
  1302          struct firmware_work *fw_work;
  1303  
  1304          fw_work = kzalloc(sizeof(struct firmware_work), gfp);
  1305          if (!fw_work)
  1306                  return -ENOMEM;
  1307  
  1308          fw_work->module = module;
  1309          fw_work->name = kstrdup_const(name, gfp);
  1310          if (!fw_work->name)

kfree(fw_work).

  1311                  return -ENOMEM;
  1312          fw_work->device = device;
  1313          fw_work->context = context;
  1314          fw_work->cont = cont;
  1315          fw_work->opt_flags = FW_OPT_NOWAIT | FW_OPT_FALLBACK |
  1316                  (uevent ? FW_OPT_UEVENT : FW_OPT_USERHELPER);
  1317  
  1318          if (!try_module_get(module)) {
  1319                  kfree_const(fw_work->name);
  1320                  kfree(fw_work);
  1321                  return -EFAULT;
  1322          }
  1323  
  1324          get_device(fw_work->device);
  1325          INIT_WORK(&fw_work->work, request_firmware_work_func);
  1326          schedule_work(&fw_work->work);
  1327          return 0;
  1328  }

regards,
dan carpenter

             reply	other threads:[~2015-05-28  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  9:02 Dan Carpenter [this message]
2015-05-29  0:45 ` firmware: fix possible use after free on name on asynchronous request Luis R. Rodriguez
2015-05-29  7:24 ` walter harms
2015-05-29 16:52 ` Luis R. Rodriguez

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=20150528090227.GA13248@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.