summaryrefslogtreecommitdiff
path: root/tools/arch/score/include/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorWill Rosenberg <whrosenb@asu.edu>2026-01-19 11:49:56 -0700
committerPeter Zijlstra <peterz@infradead.org>2026-01-21 16:28:58 +0100
commitd06bf78e55d5159c1b00072e606ab924ffbbad35 (patch)
tree49bcb077c300f7ccea7b999011d7d2a06de89d65 /tools/arch/score/include/git@git.tavy.me:linux.git
parent24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 (diff)
perf: Fix refcount warning on event->mmap_count increment
When calling refcount_inc(&event->mmap_count) inside perf_mmap_rb(), the following warning is triggered: refcount_t: addition on 0; use-after-free. WARNING: lib/refcount.c:25 PoC: struct perf_event_attr attr = {0}; int fd = syscall(__NR_perf_event_open, &attr, 0, -1, -1, 0); mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); int victim = syscall(__NR_perf_event_open, &attr, 0, -1, fd, PERF_FLAG_FD_OUTPUT); mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, victim, 0); This occurs when creating a group member event with the flag PERF_FLAG_FD_OUTPUT. The group leader should be mmap-ed and then mmap-ing the event triggers the warning. Since the event has copied the output_event in perf_event_set_output(), event->rb is set. As a result, perf_mmap_rb() calls refcount_inc(&event->mmap_count) when event->mmap_count = 0. Disallow the case when event->mmap_count = 0. This also prevents two events from updating the same user_page. Fixes: 448f97fba901 ("perf: Convert mmap() refcounts to refcount_t") Suggested-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Will Rosenberg <whrosenb@asu.edu> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://patch.msgid.link/20260119184956.801238-1-whrosenb@asu.edu
Diffstat (limited to 'tools/arch/score/include/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions