From: Jesper Juhl <jesper.juhl@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jaroslav Kysela <perex@suse.cz>, Jesper Juhl <jesper.juhl@gmail.com>
Subject: [PATCH][isapnp] Fix a potential NULL pointer dereference in isapnp_read_tag()
Date: Sun, 1 Jul 2007 01:38:31 +0200 [thread overview]
Message-ID: <200707010138.32075.jesper.juhl@gmail.com> (raw)
The Coverity checker spotted (as bug #809) that we dereference 'type'
long before we actually test it against NULL in
drivers/pnp/isapnp/core.c::isapnp_read_tag() - both branches of the
'if (tag & 0x80)' dereference type, and since this 'if' is before the test
against NULL and the return of -1, this will blow up is ever type is NULL.
This is easy to fix by simply moving the NULL test to the beginning of
the function.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
drivers/pnp/isapnp/core.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX
diff --git a/drivers/pnp/isapnp/core.c b/drivers/pnp/isapnp/core.c
index a0b1587..5696924 100644
--- a/drivers/pnp/isapnp/core.c
+++ b/drivers/pnp/isapnp/core.c
@@ -356,6 +356,8 @@ static int __init isapnp_read_tag(unsigned char *type, unsigned short *size)
{
unsigned char tag, tmp[2];
+ if (!type) /* wrong type */
+ return -1;
isapnp_peek(&tag, 1);
if (tag == 0) /* invalid tag */
return -1;
@@ -370,8 +372,6 @@ static int __init isapnp_read_tag(unsigned char *type, unsigned short *size)
#if 0
printk(KERN_DEBUG "tag = 0x%x, type = 0x%x, size = %i\n", tag, *type, *size);
#endif
- if (type == 0) /* wrong type */
- return -1;
if (*type == 0xff && *size == 0xffff) /* probably invalid data */
return -1;
return 0;
next reply other threads:[~2007-06-30 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 23:38 Jesper Juhl [this message]
2007-07-03 20:03 ` Andrew Morton
2007-07-04 1:04 ` Jesper Juhl
2007-07-04 22:59 ` [PATCH][isapnp] Remove pointless check of 'type' against 0 " Jesper Juhl
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=200707010138.32075.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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
Powered by JetHome