From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Ulrich Keil <ulrich@der-keiler.de>, linux-kernel@vger.kernel.org
Subject: Re: New do_mremap vulnerabitily.
Date: Wed, 18 Feb 2004 15:20:27 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402181516500.7318@chaos> (raw)
In-Reply-To: <4033B262.6060402@nortelnetworks.com>
On Wed, 18 Feb 2004, Chris Friesen wrote:
> Ulrich Keil wrote:
> > There was also a Proof-of-concept exploit released:
> >
> > http://www.derkeiler.com/Mailing-Lists/Securiteam/2004-02/0052.html
>
> Its a bit confusing. They talk about multiple instances of do_munmap()
> with unchecked return codes. I can only find one, in move_vma().
>
> Chris
>
Except in some drivers, you seem to be (nearly) correct ......
For Linux version 2.4.24
(file-name __follows__ the function name)
EXPORT_SYMBOL(do_munmap);
./kernel/ksyms.c
do_munmap(current->mm, addr, old_len);
do_munmap(current->mm, new_addr, new_len);
do_munmap(current->mm, addr+new_len, old_len - new_len);
./mm/mremap.c
if (!do_munmap(mm, newbrk, oldbrk-newbrk))
if (do_munmap(mm, addr, len))
* in the do_munmap, so FIXME (not in 2.4 to avoid breaking
int do_munmap(struct mm_struct *mm, unsigned long addr, size_t len)
ret = do_munmap(mm, addr, len);
if (do_munmap(mm, addr, len))
./mm/mmap.c
* do_munmap() behaves similarly, taking the range out of mm's
* exit_mmap() and do_munmap() cases described above:
./mm/swapfile.c
do_munmap(mm, shmd->vm_start, shmd->vm_end - shmd->vm_start);
******---> ./ipc/shm.c
if (do_munmap(current->mm, cont_mem.linear, size) != 0)
./drivers/char/drm/savage_drv.c
#define DO_MUNMAP(m, a, l) do_munmap(m, a, l)
./drivers/char/drm/i830_dma.c
#define DO_MUNMAP(m, a, l) do_munmap(m, a, l)
./drivers/char/drm/i810_dma.c
retcode = do_munmap(current->mm,
./drivers/char/drm-4.0/i810_dma.c
do_munmap(current->mm, newbrk, oldbrk-newbrk);
./arch/sparc/kernel/sys_sunos.c
do_munmap(mm, newbrk, oldbrk-newbrk);
./arch/mips/kernel/sysirix.c
do_munmap(current->mm, newbrk, oldbrk-newbrk);
./arch/sparc64/kernel/sys_sunos32.c
ret = do_munmap(current->mm, addr, len);
./arch/sparc64/kernel/sys_sparc.c
r = do_munmap(task->mm, ctx->ctx_smpl_vaddr, psb->psb_size);
./arch/ia64/kernel/perfmon.c
if (!do_munmap(mm, newbrk, oldbrk-newbrk))
./arch/ia64/kernel/sys_ia64.c
do_munmap(current->mm, addr, len);
./arch/s390x/kernel/linux32.c
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an Intel Pentium III machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-18 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 17:08 Ulrich Keil
2004-02-18 18:43 ` Chris Friesen
2004-02-18 20:20 ` Richard B. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 15:26 Raphael Rigo
2004-02-18 17:56 ` Linus Torvalds
2004-02-18 22:13 ` Chris Friesen
2004-02-18 22:26 ` Linus Torvalds
2004-02-18 23:49 ` Andrea Arcangeli
2004-02-18 23:46 ` Andrea Arcangeli
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=Pine.LNX.4.53.0402181516500.7318@chaos \
--to=root@chaos.analogic.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ulrich@der-keiler.de \
/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®