Menu

Star on GitHub · 3.5k

CVE-2026-93097

In the Linux kernel, the following vulnerability has been resolved: cxl/mbox: Break poison list loop on an empty payload A device that returns count == 0 with CXL_POISON_FLAG_MORE set on every it…

Published Sep 17, 2026EPSS 0.20%

Overview

CVE-2026-93097 is a known-severity vulnerability. It was published on September 17, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

cxl/mbox: Break poison list loop on an empty payload

A device that returns count == 0 with CXL_POISON_FLAG_MORE set on every

iteration never advances nr_records, so the max_errors guard never

trips and the do/while loops forever while holding poison.mutex. That

hangs the sysfs-triggered scan thread and blocks all subsequent poison

operations on the device. The existing "Protect against an uncleared

_FLAG_MORE" guard was intended to bound a misbehaving device but does

not cover the count == 0 case.

Stop the loop on an empty payload so a malfunctioning or malicious

device cannot wedge the poison scan.

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-93097?

CVE-2026-93097 is a known-severity vulnerability. It was published on September 17, 2026.

How severe is CVE-2026-93097?

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-93097?

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-93097?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-93097 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.

CyberStrike v2 is here — more intelligence, greater reach