From: Greg KH <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Tycho Andersen <tycho@tycho.pizza>,
Guixiong Wei <guixiongwei@gmail.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leaking_addresses: Provide mechanism to scan binary files
Date: Sun, 18 Feb 2024 19:07:28 +0100 [thread overview]
Message-ID: <2024021819-sacrament-violator-428d@gregkh> (raw)
In-Reply-To: <20240218173809.work.286-kees@kernel.org>
On Sun, Feb 18, 2024 at 09:38:12AM -0800, Kees Cook wrote:
> Introduce --kallsyms argument for scanning binary files for known symbol
> addresses. This would have found the exposure in /sys/kernel/notes:
>
> $ scripts/leaking_addresses.pl --kallsyms=<(sudo cat /proc/kallsyms)
> /sys/kernel/notes: hypercall_page @ 156
> /sys/kernel/notes: xen_hypercall_set_trap_table @ 156
> /sys/kernel/notes: startup_xen @ 132
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Cc: "Tobin C. Harding" <me@tobin.cc>
> Cc: Tycho Andersen <tycho@tycho.pizza>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Guixiong Wei <guixiongwei@gmail.com>
> Cc: linux-hardening@vger.kernel.org
> ---
> scripts/leaking_addresses.pl | 53 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
Nice!
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2024-02-18 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 17:38 [PATCH] leaking_addresses: Provide mechanism to scan binary files Kees Cook
2024-02-18 18:07 ` Greg KH [this message]
2024-02-22 15:24 ` Tycho Andersen
2024-02-22 21:00 ` Kees Cook
2024-02-22 21:10 ` Kees Cook
2024-02-22 23:49 ` Tycho Andersen
2024-02-29 4:40 ` Tobin Harding
2024-02-29 5:30 ` Kees Cook
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=2024021819-sacrament-violator-428d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=guixiongwei@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=tycho@tycho.pizza \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.