CVE-2026-80655: soc: xilinx: Fix race condition in event registration

CVE-2026-80655: soc: xilinx: Fix race condition in event registration

[Greg Kroah-Hartman]

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

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

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

soc: xilinx: Fix race condition in event registration

The zynqmp_power driver registers handlers for suspend and subsystem
restart events using register_event(). However, the work structures
(zynqmp_pm_init_suspend_work and zynqmp_pm_init_restart_work) used by
these handlers were allocated and initialized after the registration
call.

This created a race window where, if the firmware triggered an event
immediately after registration but before allocation, the callback
(suspend_event_callback or subsystem_restart_event_callback) would
dereference a NULL pointer in work_pending(), leading to a crash.

Fix this by allocating and initializing the work structures before
registering the events.

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


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

	Issue introduced in 6.11 with commit fcf544ac64397776a18246eba5a8ca72a47c4405 and fixed in 7.1.5 with commit d349aa118ff5e4cab88424ce1b16e08edd70f8bb
	Issue introduced in 6.11 with commit fcf544ac64397776a18246eba5a8ca72a47c4405 and fixed in 7.2 with commit fb445935338405110baca8f541a2df3b4cb8d712

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-80655
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:
	drivers/soc/xilinx/zynqmp_power.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/d349aa118ff5e4cab88424ce1b16e08edd70f8bb
	https://git.kernel.org/stable/c/fb445935338405110baca8f541a2df3b4cb8d712