mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Fixes for v6.14
Date: Tue, 8 Apr 2025 12:00:47 +0900	[thread overview]
Message-ID: <20250408120047.5c643902769ba724aaae8326@kernel.org> (raw)

Hi Linus,

Probes fixes for v6.14:

- fprobe: Fix to remove fprobe_hlist_node when module unloading

  When a fprobe target module is removed, the fprobe_hlist_node
  should be removed from the fprobe's hash table to prevent reusing
  accidentally if another module is loaded at the same address.

- fprobe: Fix to lock module while registering fprobe

 The module containing the function to be probeed is locked using a
  reference counter until the fprobe registration is complete, which
  prevents use after free.

- fprobe-events: Fix possible UAF on modules

  Basically as same as above, but in the fprobe-events layer we also
  need to get module reference counter when we find the tracepoint
  in the module.


Please pull the latest probes-fixes-v6.14 tree, which can be found at:


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

Tag SHA1: bf8e826e269fd4454c4c7df4d4d662b99466052f
Head SHA1: a3dc2983ca7b90fd35f978502de6d4664d965cfb


Masami Hiramatsu (Google) (3):
      tracing: fprobe: Fix to lock module while registering fprobe
      tracing: fprobe events: Fix possible UAF on modules
      tracing: fprobe: Cleanup fprobe hash when module unloading

----
 kernel/trace/fprobe.c       | 170 ++++++++++++++++++++++++++++++++++++++------
 kernel/trace/trace_fprobe.c |  26 ++++---
 2 files changed, 166 insertions(+), 30 deletions(-)

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

             reply	other threads:[~2025-04-08  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  3:00 Masami Hiramatsu [this message]
2025-04-08 19:54 ` pr-tracker-bot

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=20250408120047.5c643902769ba724aaae8326@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®