From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Andrey Savochkin <saw@saw.sw.com.sg>,
linux-kernel@vger.kernel.org
Subject: Re: Q about pagecache data never written to disk
Date: Thu, 09 Sep 2004 23:15:31 +1000 [thread overview]
Message-ID: <41405773.3090403@yahoo.com.au> (raw)
In-Reply-To: <20040909123957.GB1065@elf.ucw.cz>
Pavel Machek wrote:
>>No, read() will see the modified pagecache data immediately, apart from CPU
>>cache coherency effects.
>
>
> Is not this quite a big security hole?
>
> cat evil_data > /tmp/sign.me [Okay, evil_data probably have to
> contain lot of zeroes?]
> sync, fill disk or wait for someone to fill disk completely
>
> attempt to write good_data to /tmp/sign.me using mmap
>
> "Hey, root, see what /tmp/sign.me contains, can you make it suid?"
>
> root reads /tmp/sign.me, and sees it is good.
>
> root does chown root.root /tmp/sign.me; chmod 4755 /tmp/sign.me
>
> kernel realizes that there's not enough disk space, and discard
> changes, therefore /tmp/sign.me reverts to previous, evil, content.
>
root would have to make that change while user has the file open,
and should welcome the subsequent unleashing of evil content as a
valuable lesson.
next prev parent reply other threads:[~2004-09-09 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 8:01 Q about pagecache data never written to disk Andrey Savochkin
2004-09-05 9:22 ` William Lee Irwin III
2004-09-05 10:52 ` Andrew Morton
2004-09-05 11:43 ` Andrey Savochkin
2004-09-05 21:00 ` Andrew Morton
2004-09-06 7:06 ` Andrey Savochkin
2004-09-09 12:39 ` Pavel Machek
2004-09-09 13:15 ` Nick Piggin [this message]
2004-09-09 13:37 ` Pavel Machek
2004-09-09 13:32 ` Nick Piggin
2004-09-09 17:24 ` William Lee Irwin III
2004-09-09 17:14 ` Nick Piggin
2004-09-09 17:35 ` William Lee Irwin III
2004-09-05 16:33 ` William Lee Irwin III
2004-09-06 6:24 ` William Lee Irwin III
2004-09-06 7:02 ` Andrew Morton
2004-09-06 15:12 ` William Lee Irwin III
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=41405773.3090403@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=saw@saw.sw.com.sg \
/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