From: Steven Rostedt <rostedt@goodmis.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: ftrace_kill() leads to kmalloc-512 UAF
Date: Wed, 20 Jul 2022 11:40:10 -0400 [thread overview]
Message-ID: <20220720114010.20d3e0dd@gandalf.local.home> (raw)
In-Reply-To: <YtgdsW8UBSwCKtQW@localhost.localdomain>
On Wed, 20 Jul 2022 18:22:25 +0300
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> Basically, if ftrace_kill() is ever called ever there is a ticking UAFbomb.
That's because ftrace_kill() means something horribly went wrong, and
because ftrace modifies the kernel text, it shuts everything down and this
needs to be fixed.
The fix is not to have something handle ftrace_kill(), it's to fix the
situation so that ftrace_kill() is not called.
Hmm, perhaps we should add an option to make ftrace_kill() call BUG().
I'll go back and take a look at your analysis.
Thanks,
-- Steve
next prev parent reply other threads:[~2022-07-20 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 15:22 Alexey Dobriyan
2022-07-20 15:40 ` Steven Rostedt [this message]
2022-07-20 16:11 ` Steven Rostedt
2022-07-20 16:46 ` Alexey Dobriyan
2022-07-20 17:04 ` Steven Rostedt
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=20220720114010.20d3e0dd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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®