From: Dan Carpenter <dan.carpenter@oracle.com>
To: steve.glendinning@shawell.net
Cc: netdev@vger.kernel.org
Subject: re: smsc95xx: detect chip revision specific features
Date: Mon, 26 Nov 2012 23:47:22 +0300 [thread overview]
Message-ID: <20121126204722.GA26463@elgon.mountain> (raw)
Hello Steve Glendinning,
The patch 9ebca5071c86: "smsc95xx: detect chip revision specific
features" from Nov 22, 2012, leads to the following warning:
drivers/net/usb/smsc95xx.c:1349 smsc95xx_suspend()
error: buffer overflow 'filter_mask' 8 <= 31
drivers/net/usb/smsc95xx.c
1283 if (pdata->wolopts & (WAKE_BCAST | WAKE_MCAST | WAKE_ARP | WAKE_UCAST)) {
1284 u32 *filter_mask = kzalloc(32, GFP_KERNEL);
^^
We allocate 8 unsigned 32 bit values. I think this is the mistake here
actually. It is a typo and should say:
u32 *filter_mask = kzalloc(sizeof(u32) * 32, GFP_KERNEL);
If 8 elements was the intent then that's nasty.
1285 u32 command[2];
1286 u32 offset[2];
1287 u32 crc[4];
1288 int wuff_filter_count =
1289 (pdata->features & FEATURE_8_WAKEUP_FILTERS) ?
1290 LAN9500A_WUFF_NUM : LAN9500_WUFF_NUM;
LAN9500A_WUFF_NUM is 8. LAN9500_WUFF_NUM is 4.
1291 int i, filter = 0;
1292
[snip]
1348 for (i = 0; i < (wuff_filter_count * 4); i++) {
^^^^^^^^^^^^^^^^^^^^^
We are either counting to 15 or 31, and both are more that 8.
1349 ret = smsc95xx_write_reg_nopm(dev, WUFF, filter_mask[i]);
^^^^^^^^^^^^^^
So we're going past the end of the 8 element array.
1350 if (ret < 0)
1351 kfree(filter_mask);
1352 check_warn_return(ret, "Error writing WUFF\n");
1353 }
regards,
dan carpenter
next reply other threads:[~2012-11-26 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 20:47 Dan Carpenter [this message]
2012-11-27 12:32 ` smsc95xx: detect chip revision specific features Steve Glendinning
2012-11-27 12:39 ` Dan Carpenter
2012-11-27 13:21 ` Steve Glendinning
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=20121126204722.GA26463@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/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