[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250408120047.5c643902769ba724aaae8326@kernel.org>
Date: Tue, 8 Apr 2025 12:00:47 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@...nel.org>, Steven Rostedt
<rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org
Subject: [GIT PULL] probes: Fixes for v6.14
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@...nel.org>
Powered by blists - more mailing lists