Kernel use-after-free via inverted mailbox cleanup check
Published Aug 28, 2026 · Updated Aug 28, 2026
Use-after-free in the Xilinx ZynqMP power driver in Linux 5.6 allows attackers to cause kernel memory misuse via unspecified vectors. The zynqmp_pm_remove function tests !rx_chan before calling mbox_free_channel, so a valid receive channel remains active and can handle messages after its device has been removed. Exposure requires the Xilinx ZynqMP power driver, a requested mailbox receive channel, and device removal; published material establishes use-after-free and leaked channel resources but does not establish a crash, privilege gain, or code execution.
Summary
What happened
Use-after-free in the Xilinx ZynqMP power driver in Linux 5.6 allows attackers to cause kernel memory misuse via unspecified vectors. The zynqmp_pm_remove function tests !rx_chan before calling mbox_free_channel, so a valid receive channel remains active and can handle messages after its device has been removed. Exposure requires the Xilinx ZynqMP power driver, a requested mailbox receive channel, and device removal; published material establishes use-after-free and leaked channel resources but does not establish a crash, privilege gain, or code execution.
The record
- CVE
- CVE-2026-80654
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.6
- Affected versionversion=ffdbae28d9d1af70b7d63ffd7827e9795cd8d0df <a83e77d1e52c01c50096e6e97c57d34e0590d628
- Affected versionversion=ffdbae28d9d1af70b7d63ffd7827e9795cd8d0df <b0f748c563921a7918c78e6a599cefd54de7d688
- Affected versionversion=ffdbae28d9d1af70b7d63ffd7827e9795cd8d0df <b5d2240c2c7bc8370e7ba54a2e1fe3919f55aee5
- Affected versionversion=ffdbae28d9d1af70b7d63ffd7827e9795cd8d0df <fdee7c66c0d7b6869c36b9f9a915abf29ab5b550
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo