linux-cve-announce - CVE-2026-23014: perf: Ensure swevent hrtimer is properly destroyed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026012847-CVE-2026-23014-85e6@gregkh>
Date: Wed, 28 Jan 2026 15:24:48 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23014: perf: Ensure swevent hrtimer is properly destroyed

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

perf: Ensure swevent hrtimer is properly destroyed

With the change to hrtimer_try_to_cancel() in
perf_swevent_cancel_hrtimer() it appears possible for the hrtimer to
still be active by the time the event gets freed.

Make sure the event does a full hrtimer_cancel() on the free path by
installing a perf_event::destroy handler.

The Linux kernel CVE team has assigned CVE-2026-23014 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.18 with commit eb3182ef0405ff2f6668fd3e5ff9883f60ce8801 and fixed in 6.18.6 with commit deee9dfb111ab00f9dfd46c0c7e36656b80f5235
	Issue introduced in 6.18 with commit eb3182ef0405ff2f6668fd3e5ff9883f60ce8801 and fixed in 6.19-rc5 with commit ff5860f5088e9076ebcccf05a6ca709d5935cfa9
	Issue introduced in 6.17.8 with commit 6b8c512811644cf2f5eaf6f44e928683c54127f0

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-23014
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	kernel/events/core.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/deee9dfb111ab00f9dfd46c0c7e36656b80f5235
	https://git.kernel.org/stable/c/ff5860f5088e9076ebcccf05a6ca709d5935cfa9