From: Steven Rostedt <rostedt@goodmis.org>
To: Breno Leitao <leitao@debian.org>
Cc: mark.rutland@arm.com, mhiramat@kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: ftrace: UAF in ftrace_regex_open() on a removed tracing instance
Date: Fri, 28 Aug 2026 14:04:11 -0400 [thread overview]
Message-ID: <20260828140411.14108739@gandalf.local.home> (raw)
In-Reply-To: <apGwPEj65dcbZFxS@gmail.com>
On Fri, 28 Aug 2026 08:59:39 -0700
Breno Leitao <leitao@debian.org> wrote:
> ftrace_filter_open(struct inode *inode, struct file *file)
> {
> - struct ftrace_ops *ops = inode->i_private;
> + struct trace_array *tr = inode->i_private;
> + int ret;
>
> - /* Checks for tracefs lockdown */
> - return ftrace_regex_open(ops,
> - FTRACE_ITER_FILTER | FTRACE_ITER_DO_PROBES,
> - inode, file);
> + /* Checks for tracefs lockdown, and that the instance is still alive */
> + ret = tracing_check_open_get_tr(tr);
> + if (ret)
> + return ret;
> +
> + ret = ftrace_regex_open(tr->ops,
> + FTRACE_ITER_FILTER | FTRACE_ITER_DO_PROBES,
> + inode, file);
> + /* ftrace_regex_open() holds its own reference on success */
Hmm, I just noticed this part (from reviewing my own code first, and then
looking at what your AI did).
I guess the issue is that the ops may be freed before you get access to the
trace array. Anyway more needs to be changed. I may remove the extra
reference. No need to do it twice. Also since trace_stack may have the
issue too.
-- Steve
> + trace_array_put(tr);
> + return ret;
> }
next prev parent reply other threads:[~2026-08-28 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 13:38 ftrace: UAF in ftrace_regex_open() on a removed tracing instance Breno Leitao
2026-08-28 14:42 ` Steven Rostedt
2026-08-28 15:59 ` Breno Leitao
2026-08-28 16:34 ` Steven Rostedt
2026-08-28 16:34 ` Steven Rostedt
2026-08-28 17:49 ` Steven Rostedt
2026-08-28 18:04 ` Steven Rostedt [this message]
2026-08-28 19:55 ` 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=20260828140411.14108739@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=leitao@debian.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
/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).