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

> A race condition in the Xilinx ZynqMP power driver allows a local attacker to trigger a kernel crash via NULL pointer dereference.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-80655, DEBIAN-CVE-2026-80655, GHSA-x28x-mxhh-x47j, UBUNTU-CVE-2026-80655

## What is CVE-2026-80655?

CVE-2026-80655 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80655?


## How do I fix CVE-2026-80655?

Apply the vendor's patch.

## Is CVE-2026-80655 being exploited?

There is no known exploitation of CVE-2026-80655 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80655 and fix it if it is affected.

What it is: CVE-2026-80655 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80655 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80655/ (Markdown: https://insights.sbomify.com/CVE-2026-80655/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80655
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80655
- OSV: https://osv.dev/vulnerability/CVE-2026-80655

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80655/
Summaries are generated and may contain mistakes; the official description above is the record.