# CVE-2026-80654: soc: xilinx: Shutdown and free rx mailbox channel

> A use-after-free vulnerability in the Xilinx SoC mailbox driver allows local attackers to execute arbitrary code or escalate privileges due to improper channel cleanup.

- **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:** AZL-98090, BELL-CVE-2026-80654, DEBIAN-CVE-2026-80654, GHSA-79cq-96j4-g3x2, UBUNTU-CVE-2026-80654

## What is CVE-2026-80654?

CVE-2026-80654 is an use after free 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: Shutdown and free rx mailbox channel

A mbox rx channel is requested using mbox_request_channel_byname() in
probe. In remove callback, the rx mailbox channel is cleaned up when the
rx_chan is NULL due to incorrect condition check. The mailbox channel is
not shutdown and it can receive messages even after the device removal.
This leads to use after free. Also the channel resources are not freed.
Fix this by checking the rx_chan correctly.

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


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

Apply the vendor's patch.

## Is CVE-2026-80654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80654 is an use after free 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-80654 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-80654/ (Markdown: https://insights.sbomify.com/CVE-2026-80654/index.md)
```

## Sources

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

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