This is a note to let you know that I've just added the patch titled
staging: comedi: don't dereference user memory for INSN_INTTRIG
to the 3.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
staging-comedi-don-t-dereference-user-memory-for-insn_inttrig.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 5d06e3df280bd230e2eadc16372e62818c63e894 Mon Sep 17 00:00:00 2001
From: Ian Abbott <[email protected]>
Date: Tue, 18 Sep 2012 19:46:58 +0100
Subject: staging: comedi: don't dereference user memory for INSN_INTTRIG
From: Ian Abbott <[email protected]>
commit 5d06e3df280bd230e2eadc16372e62818c63e894 upstream.
`parse_insn()` is dereferencing the user-space pointer `insn->data`
directly when handling the `INSN_INTTRIG` comedi instruction. It
shouldn't be using `insn->data` at all; it should be using the separate
`data` pointer passed to the function. Fix it.
Signed-off-by: Ian Abbott <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/staging/comedi/comedi_fops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/comedi/comedi_fops.c
+++ b/drivers/staging/comedi/comedi_fops.c
@@ -951,7 +951,7 @@ static int parse_insn(struct comedi_devi
ret = -EAGAIN;
break;
}
- ret = s->async->inttrig(dev, s, insn->data[0]);
+ ret = s->async->inttrig(dev, s, data[0]);
if (ret >= 0)
ret = 1;
break;
Patches currently in stable-queue which might be from [email protected] are
queue-3.6/staging-comedi-s626-don-t-dereference-insn-data.patch
queue-3.6/staging-comedi-jr3_pci-fix-iomem-dereference.patch
queue-3.6/staging-comedi-fix-memory-leak-for-saved-channel-list.patch
queue-3.6/staging-comedi-don-t-dereference-user-memory-for-insn_inttrig.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
