From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: kernel-hardening@lists.openwall.com,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Theodore Ts'o <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Tycho Andersen <tycho@docker.com>,
"Roberts, William C" <william.c.roberts@intel.com>,
Tejun Heo <tj@kernel.org>,
Jordan Glover <Golden_Miller83@protonmail.ch>,
Greg KH <gregkh@linuxfoundation.org>,
Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>,
Ian Campbell <ijc@hellion.org.uk>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <wilal.deacon@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Chris Fries <cfries@google.com>,
Dave Weinstein <olorin@goo
Subject: Re: [PATCH v4] scripts: add leaking_addresses.pl
Date: Sun, 12 Nov 2017 02:10:07 +0300 [thread overview]
Message-ID: <20171111231007.iirqce3r7xqqnxd3@node.shutemov.name> (raw)
In-Reply-To: <1510050731-32446-1-git-send-email-me@tobin.cc>
On Tue, Nov 07, 2017 at 09:32:11PM +1100, Tobin C. Harding wrote:
> Currently we are leaking addresses from the kernel to user space. This
> script is an attempt to find some of those leakages. Script parses
> `dmesg` output and /proc and /sys files for hex strings that look like
> kernel addresses.
>
> Only works for 64 bit kernels, the reason being that kernel addresses
> on 64 bit kernels have 'ffff' as the leading bit pattern making greping
> possible. On 32 kernels we don't have this luxury.
Well, it's not going to work as well as intented on x86 machine with
5-level paging. Kernel address space there starts at 0xff10000000000000.
It will still catch pointers to kernel/modules text, but the rest is
outside of 0xffff... space. See Documentation/x86/x86_64/mm.txt.
Not sure if we care. It won't work too for other 64-bit architectrues that
have more than 256TB of virtual address space.
Just wanted to point to the limitation.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2017-11-11 23:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 10:32 [PATCH v4] scripts: add leaking_addresses.pl Tobin C. Harding
2017-11-07 10:50 ` Greg KH
2017-11-07 20:51 ` Tobin C. Harding
2017-11-07 13:56 ` David Laight
2017-11-07 20:58 ` Tobin C. Harding
2017-11-07 21:11 ` Linus Torvalds
2017-11-07 15:51 ` Petr Mladek
2017-11-07 20:39 ` Tobin C. Harding
2017-11-07 23:36 ` [kernel-hardening] " Laura Abbott
2017-11-08 0:59 ` Linus Torvalds
2017-11-08 20:39 ` Linus Torvalds
2017-11-09 4:43 ` Kaiwan N Billimoria
2017-11-09 4:54 ` Kaiwan N Billimoria
2017-11-09 18:11 ` Steven Rostedt
2017-11-10 3:03 ` Kaiwan N Billimoria
2017-11-08 1:13 ` Tobin C. Harding
2017-11-08 12:10 ` [kernel-hardening] " Michael Ellerman
2017-11-08 21:16 ` Tobin C. Harding
2017-11-08 22:48 ` Tobin C. Harding
2017-11-09 0:49 ` Michael Ellerman
2017-11-09 2:08 ` Tobin C. Harding
2017-11-10 22:12 ` [kernel-hardening] " Frank Rowand
2017-11-12 11:49 ` Michael Ellerman
2017-11-12 18:02 ` Frank Rowand
2017-11-12 21:18 ` Tobin C. Harding
2017-11-13 1:06 ` Michael Ellerman
2017-11-10 13:56 ` kaiwan.billimoria
2017-11-12 22:21 ` Tobin C. Harding
2017-11-13 5:46 ` kaiwan.billimoria
2017-11-13 6:08 ` Tobin C. Harding
2017-11-13 6:52 ` Kaiwan N Billimoria
2017-11-20 15:39 ` Petr Mladek
2017-11-19 23:56 ` Tobin C. Harding
2017-11-11 23:10 ` Kirill A. Shutemov [this message]
2017-11-12 23:06 ` Tobin C. Harding
2017-11-13 3:37 ` Kirill A. Shutemov
2017-11-13 4:35 ` Tobin C. Harding
2017-11-13 5:27 ` [kernel-hardening] " Kaiwan N Billimoria
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=20171111231007.iirqce3r7xqqnxd3@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=Golden_Miller83@protonmail.ch \
--cc=Jason@zx2c4.com \
--cc=catalin.marinas@arm.com \
--cc=cfries@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ijc@hellion.org.uk \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=me@tobin.cc \
--cc=olorin@goo \
--cc=pbonzini@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tycho@docker.com \
--cc=tytso@mit.edu \
--cc=wilal.deacon@arm.com \
--cc=william.c.roberts@intel.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;
as well as URLs for NNTP newsgroup(s).