From: Stephen Hemminger <stephen@networkplumber.org>
To: Greg KH <greg@kroah.com>
Cc: linux-pci@vger.kernel.org
Subject: PCI dynamic id use after free?
Date: Thu, 7 Apr 2016 10:15:59 -0700 [thread overview]
Message-ID: <20160407101559.445760c0@xeon-e3> (raw)
I was looking at another PCI problem, and discovered this potential use
after kfree.
static const struct pci_device_id *pci_match_device(struct pci_driver *drv,
struct pci_dev *dev)
{
struct pci_dynid *dynid;
const struct pci_device_id *found_id = NULL;
/* When driver_override is set, only bind to the matching driver */
if (dev->driver_override && strcmp(dev->driver_override, drv->name))
return NULL;
/* Look at the dynamic ids first, before the static ones */
spin_lock(&drv->dynids.lock);
list_for_each_entry(dynid, &drv->dynids.list, node) {
if (pci_match_one_device(&dynid->id, dev)) {
found_id = &dynid->id;
break;
}
}
spin_unlock(&drv->dynids.lock);
At this point found_id if matched (points into dynid) structure but the
lock has been dropped.
What prevents the ID from being removed by store_remvoe_id?
Looks like you need RCU (or ref counts here).
next reply other threads:[~2016-04-07 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 17:15 Stephen Hemminger [this message]
2016-04-07 18:35 ` PCI dynamic id use after free? Greg KH
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=20160407101559.445760c0@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=greg@kroah.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).