From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Ernie Petrides <petrides@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch] fix for memory corruption from /proc/kcore access
Date: Thu, 3 Feb 2005 13:16:59 -0200 [thread overview]
Message-ID: <20050203151659.GB27727@logos.cnet> (raw)
In-Reply-To: <200502030219.j132JsTi013377@pasta.boston.redhat.com>
Hi Ernie,
On Wed, Feb 02, 2005 at 09:19:54PM -0500, Ernie Petrides wrote:
> Hi, Marcelo. A fairly nasty memory corruption potential exists when
> /proc/kcore is accessed and there are at least 62 vmalloc'd areas.
>
> The problem is that get_kcore_size() does not properly account for
> the elf_prstatus, elf_prpsinfo, and task_struct structure sizes in
> the fabricated ELF header, and then elf_kcore_store_hdr() and its
> associated calls to storenote() will possibly overrun the "elf_buf"
> buffer allocated by read_kcore(). Because the requested buffer size
> is rounded up to a page multiple, only certain ranges of counts of
> vmalloc'd areas will actually lead to a memory corruption. When it
> does happen, usually the end of the /proc/kcore reader's task_struct
> ends up being copied into a slab page (or sometimes into a data page)
> causing a kernel crash (or data corruption) at a later point in time.
Ouch.
> The 1st hunk of the patch below fixes this problem. The latter 3
> hunks correct the "p_filesz" value for the note section (which is
> already initialized to 0 on line 232) as stored in the ELF header,
> but these hunks are not necessary to fix the corruption possiblity.
Looks OK to me.
> The fix is already in 2.6.
Applied, cheers!
>
> Cheers. -ernie
>
>
>
> --- linux-2.4.29/fs/proc/kcore.c.orig 2004-08-07 19:26:06.000000000 -0400
> +++ linux-2.4.29/fs/proc/kcore.c 2005-02-02 19:52:50.000000000 -0500
> @@ -136,7 +136,10 @@ static unsigned long get_kcore_size(int
> }
> *elf_buflen = sizeof(struct elfhdr) +
> (*num_vma + 2)*sizeof(struct elf_phdr) +
> - 3 * sizeof(struct memelfnote);
> + 3 * (sizeof(struct elf_note) + 4) +
> + sizeof(struct elf_prstatus) +
> + sizeof(struct elf_prpsinfo) +
> + sizeof(struct task_struct);
> *elf_buflen = PAGE_ALIGN(*elf_buflen);
> return (size - PAGE_OFFSET + *elf_buflen);
> }
> @@ -279,7 +282,7 @@ static void elf_kcore_store_hdr(char *bu
>
> memset(&prstatus, 0, sizeof(struct elf_prstatus));
>
> - nhdr->p_filesz = notesize(¬es[0]);
> + nhdr->p_filesz += notesize(¬es[0]);
> bufp = storenote(¬es[0], bufp);
>
> /* set up the process info */
> @@ -296,7 +299,7 @@ static void elf_kcore_store_hdr(char *bu
> strcpy(prpsinfo.pr_fname, "vmlinux");
> strncpy(prpsinfo.pr_psargs, saved_command_line, ELF_PRARGSZ);
>
> - nhdr->p_filesz = notesize(¬es[1]);
> + nhdr->p_filesz += notesize(¬es[1]);
> bufp = storenote(¬es[1], bufp);
>
> /* set up the task structure */
> @@ -305,7 +308,7 @@ static void elf_kcore_store_hdr(char *bu
> notes[2].datasz = sizeof(struct task_struct);
> notes[2].data = current;
>
> - nhdr->p_filesz = notesize(¬es[2]);
> + nhdr->p_filesz += notesize(¬es[2]);
> bufp = storenote(¬es[2], bufp);
>
> } /* end elf_kcore_store_hdr() */
prev parent reply other threads:[~2005-02-03 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 2:19 Ernie Petrides
2005-02-03 15:16 ` Marcelo Tosatti [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=20050203151659.GB27727@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petrides@redhat.com \
/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
all inboxes | Powered by JetHome®