From: Alex Elder <elder@inktank.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] lib/parser.c: avoid overflow in match_number()
Date: Thu, 09 Aug 2012 13:03:41 -0700 [thread overview]
Message-ID: <5024179D.30308@inktank.com> (raw)
The result of converting an integer value to another signed integer
type that's unable to represent the original value is implementation
defined. (See notes in section 6.3.1.3 of the C standard.)
In match_number(), the result of simple_strtol() (which returns type
long) is assigned to a value of type int.
Instead, handle the result of simple_strtol() in a well-defined way,
and return -ERANGE if the result won't fit in the int variable used
to hold the parsed result.
No current callers pay attention to the particular error value
returned, so this additional return code shouldn't do any harm.
Signed-off-by: Alex Elder <elder@inktank.com>
---
lib/parser.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
Index: b/lib/parser.c
===================================================================
--- a/lib/parser.c
+++ b/lib/parser.c
@@ -122,13 +122,14 @@ int match_token(char *s, const match_tab
*
* Description: Given a &substring_t and a base, attempts to parse the
substring
* as a number in that base. On success, sets @result to the integer
represented
- * by the string and returns 0. Returns either -ENOMEM or -EINVAL on
failure.
+ * by the string and returns 0. Returns -ENOMEM, -EINVAL, or -ERANGE on
failure.
*/
static int match_number(substring_t *s, int *result, int base)
{
char *endp;
char *buf;
int ret;
+ long val;
size_t len = s->to - s->from;
buf = kmalloc(len + 1, GFP_KERNEL);
@@ -136,10 +137,15 @@ static int match_number(substring_t *s,
return -ENOMEM;
memcpy(buf, s->from, len);
buf[len] = '\0';
- *result = simple_strtol(buf, &endp, base);
+
ret = 0;
+ val = simple_strtol(buf, &endp, base);
if (endp == buf)
ret = -EINVAL;
+ else if (val < (long) INT_MIN || val > (long) INT_MAX)
+ ret = -ERANGE;
+ else
+ *result = (int) val;
kfree(buf);
return ret;
}
next reply other threads:[~2012-08-09 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 20:03 Alex Elder [this message]
2012-08-10 17:26 ` [PATCH] lib/parser.c: avoid overflow in match_number() Randy Dunlap
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=5024179D.30308@inktank.com \
--to=elder@inktank.com \
--cc=linux-kernel@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).