CVE-2026-80655: Linux kernel · soc: xilinx: Fix race condition in event registration
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fb445935338405110baca8f541a2df3b4cb8d712 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fb445935338405110baca8f541a2df3b4cb8d712, e124f7b170337563d78a7a6aa152c897d229bc39, d349aa118ff5e4cab88424ce1b16e08edd70f8bb +1
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to fb445935338405110baca8f541a2df3b4cb8d712, e124f7b170337563d78a7a6aa152c897d229bc39, d349aa118ff5e4cab88424ce1b16e08edd70f8bb or 07ea9081b8fefb99e2f427e0f0602a5e576cb120.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/07ea9081b8fefb99e2f427e0f0602a5e576cb120 (opens in a new tab)
- git.kernel.org/stable/c/e124f7b170337563d78a7a6aa152c897d229bc39 (opens in a new tab)
- git.kernel.org/stable/c/d349aa118ff5e4cab88424ce1b16e08edd70f8bb (opens in a new tab)
- git.kernel.org/stable/c/fb445935338405110baca8f541a2df3b4cb8d712 (opens in a new tab)