The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/2] tracing: More fixes for v7.2
Date: Tue, 07 Jul 2026 19:34:21 -0400	[thread overview]
Message-ID: <20260707233421.684046879@kernel.org> (raw)

tracing fixes for 7.2:

- Fix use-after-free in user_event_mm_dup()

  When the enabler is removed from the link list, it is freed immediately.
  But it is protected via RCU and needs to be freed after an RCU
  grace period. Use queue_rcu_work() so that the event_mutex can also
  be taken as user_event_put() takes the mutex on the last reference
  is released.

- Free type string in error path of parse_synth_field()

  There's an error path in parse_synth_field() where the allocated type
  string is not freed.


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes

Head SHA1: 05074bb90af94f2acbbc8f8ffaa507f914c273c8


Michael Bommarito (1):
      tracing/user_events: Fix use-after-free in user_event_mm_dup()

Yu Peng (1):
      tracing/synthetic: Free type string on error path

----
 kernel/trace/trace_events_synth.c |  4 +++-
 kernel/trace/trace_events_user.c  | 39 ++++++++++++++++++++++++++++++++-------
 2 files changed, 35 insertions(+), 8 deletions(-)

             reply	other threads:[~2026-07-07 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 23:34 Steven Rostedt [this message]
2026-07-07 23:34 ` [for-linus][PATCH 1/2] tracing/user_events: Fix use-after-free in user_event_mm_dup() Steven Rostedt
2026-07-07 23:34 ` [for-linus][PATCH 2/2] tracing/synthetic: Free type string on error path 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=20260707233421.684046879@kernel.org \
    --to=rostedt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.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