From: Ducrot Bruno <ducrot@arm.linux.org.uk>
To: cpufreq@www.linux.org.uk
Subject: cpufreq/linux/drivers/cpufreq userspace.c,1.1.1.2,1.1.1.3
Date: Thu, 15 Jul 2004 14:08:05 +0100 [thread overview]
Message-ID: <E1Bl5y1-0002Md-NG@flint.arm.linux.org.uk> (raw)
Update of /mnt/src/cvsroot/cpufreq/linux/drivers/cpufreq
In directory flint:/tmp/cvs-serv9074
Modified Files:
Tag: LINUX_2_4
userspace.c
Log Message:
Fix security hole in proc handler.
Brad Spengler <spender@grsecurity.net> found an exploitable bug in the proc handler
of cpufreq, where a user-supplied unsigned int is cast to a signed int and then
passed on to copy_[to|from]_user() allowing arbitary amounts of memory to be written
(root only thankfully), or read (as any user).
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the name CAN-2004-0228 to this issue.
Index: userspace.c
===================================================================
RCS file: /mnt/src/cvsroot/cpufreq/linux/drivers/cpufreq/Attic/userspace.c,v
retrieving revision 1.1.1.2
retrieving revision 1.1.1.3
diff -u -r1.1.1.2 -r1.1.1.3
--- userspace.c 28 Aug 2003 13:41:57 -0000 1.1.1.2
+++ userspace.c 15 Jul 2004 13:08:02 -0000 1.1.1.3
@@ -161,7 +161,7 @@
{
char buf[16], *p;
int cpu = (int) ctl->extra1;
- int len, left = *lenp;
+ size_t len, left = *lenp;
if (!left || (filp->f_pos && !write) || !cpu_online(cpu)) {
*lenp = 0;
reply other threads:[~2004-07-15 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Bl5y1-0002Md-NG@flint.arm.linux.org.uk \
--to=ducrot@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
/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.