From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
kitta <kitta@linux.alibaba.com>,
Evan Li <evan.li@linux.alibaba.com>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org
Subject: Re: [tip: perf/urgent] perf/x86/intel: Fix NULL event dereference crash in handle_pmi_common()
Date: Sat, 13 Dec 2025 13:06:01 +0100 [thread overview]
Message-ID: <20251213120601.GQ3911114@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <176553028144.498.11236460229358296060.tip-bot2@tip-bot2>
On Fri, Dec 12, 2025 at 09:04:41AM -0000, tip-bot2 for Evan Li wrote:
> The following commit has been merged into the perf/urgent branch of tip:
>
> Commit-ID: 9415f749d34b926b9e4853da1462f4d941f89a0d
> Gitweb: https://git.kernel.org/tip/9415f749d34b926b9e4853da1462f4d941f89a0d
> Author: Evan Li <evan.li@linux.alibaba.com>
> AuthorDate: Fri, 12 Dec 2025 16:49:43 +08:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 12 Dec 2025 09:57:39 +01:00
>
> perf/x86/intel: Fix NULL event dereference crash in handle_pmi_common()
>
> handle_pmi_common() may observe an active bit set in cpuc->active_mask
> while the corresponding cpuc->events[] entry has already been cleared,
> which leads to a NULL pointer dereference.
>
> This can happen when interrupt throttling stops all events in a group
> while PEBS processing is still in progress. perf_event_overflow() can
> trigger perf_event_throttle_group(), which stops the group and clears
> the cpuc->events[] entry, but the active bit may still be set when
> handle_pmi_common() iterates over the events.
>
> The following recent fix:
>
> 7e772a93eb61 ("perf/x86: Fix NULL event access and potential PEBS record loss")
>
> moved the cpuc->events[] clearing from x86_pmu_stop() to x86_pmu_del() and
> relied on cpuc->active_mask/pebs_enabled checks. However,
> handle_pmi_common() can still encounter a NULL cpuc->events[] entry
> despite the active bit being set.
>
> Add an explicit NULL check on the event pointer before using it,
> to cover this legitimate scenario and avoid the NULL dereference crash.
>
> Fixes: 7e772a93eb61 ("perf/x86: Fix NULL event access and potential PEBS record loss")
> Reported-by: kitta <kitta@linux.alibaba.com>
> Co-developed-by: kitta <kitta@linux.alibaba.com>
> Signed-off-by: Evan Li <evan.li@linux.alibaba.com>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Link: https://patch.msgid.link/20251212084943.2124787-1-evan.li@linux.alibaba.com
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220855
> ---
> arch/x86/events/intel/core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 853fe07..bdf3f0d 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -3378,6 +3378,9 @@ static int handle_pmi_common(struct pt_regs *regs, u64 status)
>
> if (!test_bit(bit, cpuc->active_mask))
> continue;
> + /* Event may have already been cleared: */
> + if (!event)
> + continue;
I still hate this commit -- it doesn't actually explain anything, at
best it papers over an issue elsewhere :-(
next prev parent reply other threads:[~2025-12-13 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 8:49 [PATCH] perf/x86: Prevent NULL event deref in handle_pmi_common() evan.li
2025-12-12 9:04 ` [tip: perf/urgent] perf/x86/intel: Fix NULL event dereference crash " tip-bot2 for Evan Li
2025-12-13 12:06 ` Peter Zijlstra [this message]
2025-12-12 10:44 ` [PATCH] perf/x86: Prevent NULL event deref " Peter Zijlstra
2025-12-15 7:43 ` Mi, Dapeng
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=20251213120601.GQ3911114@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=evan.li@linux.alibaba.com \
--cc=kitta@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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