From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [patch] tehuti: using uninitialized data in bdx_ioctl_priv()
Date: Mon, 24 Jun 2013 19:05:03 +0300 [thread overview]
Message-ID: <20130624160503.GC31984@elgon.mountain> (raw)
If we "cmd == SIOCDEVPRIVATE" then we use data[] without initializing
it. The most common case is that we would return -EOPNOTSUPP. The
other case is that we'd end up reading and writing to randomish places.
This requires CAP_SYS_RAWIO so it's not very bad.
The fix is to not allow SIOCDEVPRIVATE because it doesn't work. I
returned -EOPNOTSUPP instead of -ENOTTY because that's what is used in
the rest of the file.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
---
This bug is several years old.
diff --git a/drivers/net/ethernet/tehuti/tehuti.c b/drivers/net/ethernet/tehuti/tehuti.c
index 571452e..5d08f38 100644
--- a/drivers/net/ethernet/tehuti/tehuti.c
+++ b/drivers/net/ethernet/tehuti/tehuti.c
@@ -647,14 +647,16 @@ static int bdx_ioctl_priv(struct net_device *ndev, struct ifreq *ifr, int cmd)
ENTER;
DBG("jiffies=%ld cmd=%d\n", jiffies, cmd);
- if (cmd != SIOCDEVPRIVATE) {
- error = copy_from_user(data, ifr->ifr_data, sizeof(data));
- if (error) {
- pr_err("can't copy from user\n");
- RET(-EFAULT);
- }
- DBG("%d 0x%x 0x%x\n", data[0], data[1], data[2]);
+
+ if (cmd == SIOCDEVPRIVATE)
+ RET(-EOPNOTSUPP);
+
+ error = copy_from_user(data, ifr->ifr_data, sizeof(data));
+ if (error) {
+ pr_err("can't copy from user\n");
+ RET(-EFAULT);
}
+ DBG("%d 0x%x 0x%x\n", data[0], data[1], data[2]);
if (!capable(CAP_SYS_RAWIO))
return -EPERM;
next reply other threads:[~2013-06-24 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:05 Dan Carpenter [this message]
2013-06-24 20:01 ` [patch] tehuti: using uninitialized data in bdx_ioctl_priv() David Miller
2013-06-24 20:24 ` Ben Hutchings
2013-06-24 23:27 ` David Miller
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=20130624160503.GC31984@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=andy@greyhouse.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@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