From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Christoph Fritz <chf.fritz@googlemail.com>,
linux-pcmcia@lists.infradead.org
Cc: linux-next <linux-next@vger.kernel.org>
Subject: [PATCH] pcmcia: avoid buffer overflow in pcmcia_setup_isa_irq
Date: Tue, 3 Aug 2010 09:40:22 +0200 [thread overview]
Message-ID: <20100803074022.GA28158@comet.dominikbrodowski.net> (raw)
In-Reply-To: <1280795899.11158.52.camel@lovely.krouter>
On Tue, Aug 03, 2010 at 02:38:19AM +0200, Christoph Fritz wrote:
> Hi,
>
> buffer overflow in next-tree's commit 6f0f38c45a8f2f511c25893e33011ff32fc811db:
> size of array pcmcia_used_irq[] can be less than 32
>
> in drivers/pcmcia/pcmcia_resource.c
> +static int pcmcia_setup_isa_irq(struct pcmcia_device *p_dev, int type)
> +{
> [..]
> + for (try = 0; try < 64; try++) {
> + irq = try % 32;
> [..]
> +
> + /* avoid an IRQ which is already used by another PCMCIA card */
> + if ((try < 32) && pcmcia_used_irq[irq])
> + continue;
>
> drivers/pcmcia/pcmcia_resource.c
> static u8 pcmcia_used_irq[NR_IRQS];
>
> arch/x86/include/asm/irq_vectors.h
> #define NR_IRQS_LEGACY 16
> [..]
> #else /* !CONFIG_X86_IO_APIC: */
> # define NR_IRQS NR_IRQS_LEGACY
> #endif
>
> ---
> non-tested fix:
What about this?
[PATCH] pcmcia: avoid buffer overflow in pcmcia_setup_isa_irq
NR_IRQS may be as low as 16, causing a (harmless?) buffer overflow in
pcmcia_setup_isa_irq():
static u8 pcmcia_used_irq[NR_IRQS];
...
if ((try < 32) && pcmcia_used_irq[irq])
continue;
This is read-only, so if this address would be non-zero, it would just
mean we would not attempt an IRQ >= NR_IRQS -- which would fail anyway!
And as request_irq() fails for an irq >= NR_IRQS, the setting code path:
pcmcia_used_irq[irq]++;
is never reached as well.
Reported-by: Christoph Fritz <chf.fritz@googlemail.com>
CC: stable@kernel.org
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
diff --git a/drivers/pcmcia/pcmcia_resource.c b/drivers/pcmcia/pcmcia_resource.c
index d48437f..54aa1c2 100644
--- a/drivers/pcmcia/pcmcia_resource.c
+++ b/drivers/pcmcia/pcmcia_resource.c
@@ -677,7 +677,7 @@ EXPORT_SYMBOL(__pcmcia_request_exclusive_irq);
#ifdef CONFIG_PCMCIA_PROBE
/* mask of IRQs already reserved by other cards, we should avoid using them */
-static u8 pcmcia_used_irq[NR_IRQS];
+static u8 pcmcia_used_irq[32];
static irqreturn_t test_action(int cpl, void *dev_id)
{
@@ -700,6 +700,9 @@ static int pcmcia_setup_isa_irq(struct pcmcia_device *p_dev, int type)
for (try = 0; try < 64; try++) {
irq = try % 32;
+ if (irq > NR_IRQS)
+ continue;
+
/* marked as available by driver, not blocked by userspace? */
if (!((mask >> irq) & 1))
continue;
next prev parent reply other threads:[~2010-08-03 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 0:38 [BUG -next] pcmcia: setup IRQ to be used by PCMCIA drivers at card insert Christoph Fritz
2010-08-03 6:17 ` Dominik Brodowski
2010-08-03 10:23 ` Christoph Fritz
2010-08-03 7:40 ` Dominik Brodowski [this message]
2010-08-03 7:42 ` [PATCH] pcmcia: avoid buffer overflow in pcmcia_setup_isa_irq Dominik Brodowski
2010-08-03 10:26 ` Christoph Fritz
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=20100803074022.GA28158@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=chf.fritz@googlemail.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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