Menu

Star on GitHub · 3.2k

CVE-2026-80654

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.

Published Aug 28, 2026EPSS 0.21%

Overview

CVE-2026-80654 is a known-severity vulnerability. It was published on August 28, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80654?

CVE-2026-80654 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-80654?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80654?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80654?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80654 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.