From: Dan Rosenberg <drosenberg@vsecurity.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] ALSA: asihpi - off by one in asihpi_hpi_ioctl()
Date: Wed, 27 Jul 2011 13:02:13 +0000 [thread overview]
Message-ID: <1311771733.2125.9.camel@osiris> (raw)
In-Reply-To: <20110727120226.GP3824@shale.localdomain>
> > Also it moved the initialization of "pa" down a couple lines so I'm
> > concerned there may be a bogus derereference here when we check
> > pa->type. I don't have the hardware, so I can't test this.
> >
>
> I agree. This code seems to make assumptions in more than one place
> that the adapters array is fully populated with non-NULL elements. At a
> glance, I can't see where such initialization occurs though.
>
I hadn't read the updated code fully, so I missed what you meant. Yes,
this is definitely a NULL dereference, since "pa" is initialized to NULL
and not changed until after this dereference.
> > diff --git a/sound/pci/asihpi/hpioctl.c b/sound/pci/asihpi/hpioctl.c
> > index 65fcf47..7ba7073 100644
> > --- a/sound/pci/asihpi/hpioctl.c
> > +++ b/sound/pci/asihpi/hpioctl.c
> > @@ -183,7 +183,7 @@ long asihpi_hpi_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> > int wrflag = -1;
> > u32 adapter = hm->h.adapter_index;
> >
> > - if ((adapter > HPI_MAX_ADAPTERS) || (!pa->type)) {
> > + if ((adapter >= HPI_MAX_ADAPTERS) || (!pa->type)) {
> > hpi_init_response(&hr->r0, HPI_OBJ_ADAPTER,
> > HPI_ADAPTER_OPEN,
> > HPI_ERROR_BAD_ADAPTER_NUMBER);
>
next prev parent reply other threads:[~2011-07-27 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:02 [patch] ALSA: asihpi - off by one in asihpi_hpi_ioctl() Dan Carpenter
2011-07-27 12:02 ` Dan Carpenter
2011-07-27 12:55 ` Dan Rosenberg
2011-07-27 21:45 ` Eliot Blennerhassett
2011-07-27 21:45 ` Eliot Blennerhassett
2011-07-27 13:02 ` Dan Rosenberg [this message]
2011-07-27 13:06 ` Takashi Iwai
2011-07-27 13:06 ` Takashi Iwai
2011-07-27 14:05 ` Takashi Iwai
2011-07-27 14:05 ` Takashi Iwai
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=1311771733.2125.9.camel@osiris \
--to=drosenberg@vsecurity.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.