From: Richard Weinberger <richard@nod.at>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Fabian Yamaguchi <fabs@goesec.de>,
security@kernel.org, user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
user-mode-linux-user@lists.sourceforge.net,
Nico Golde <nico@ngolde.de>
Subject: Re: [uml-devel] [patch] uml: check length in exitcode_proc_write()
Date: Fri, 01 Nov 2013 10:22:12 +0100 [thread overview]
Message-ID: <527372C4.2080706@nod.at> (raw)
In-Reply-To: <20131029190604.GA21820@longonot.mountain>
Am 29.10.2013 20:06, schrieb Dan Carpenter:
> We don't cap the size of buffer from the user so we could write past
> the end of the array here. Only root can write to this file.
>
> Reported-by: Nico Golde <nico@ngolde.de>
> Reported-by: Fabian Yamaguchi <fabs@goesec.de>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks everyone!
Patch applied and an it's way to Linus' tree.
Thanks,
//richard
> diff --git a/arch/um/kernel/exitcode.c b/arch/um/kernel/exitcode.c
> index 829df49..41ebbfe 100644
> --- a/arch/um/kernel/exitcode.c
> +++ b/arch/um/kernel/exitcode.c
> @@ -40,9 +40,11 @@ static ssize_t exitcode_proc_write(struct file *file,
> const char __user *buffer, size_t count, loff_t *pos)
> {
> char *end, buf[sizeof("nnnnn\0")];
> + size_t size;
> int tmp;
>
> - if (copy_from_user(buf, buffer, count))
> + size = min(count, sizeof(buf));
> + if (copy_from_user(buf, buffer, size))
> return -EFAULT;
>
> tmp = simple_strtol(buf, &end, 0);
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2013-11-01 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131025144452.GA28451@ngolde.de>
2013-10-29 19:06 ` [uml-devel] [patch] uml: check length in exitcode_proc_write() Dan Carpenter
2013-11-01 9:22 ` Richard Weinberger [this message]
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=527372C4.2080706@nod.at \
--to=richard@nod.at \
--cc=dan.carpenter@oracle.com \
--cc=fabs@goesec.de \
--cc=jdike@addtoit.com \
--cc=nico@ngolde.de \
--cc=security@kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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