CVE-2023-20593, known as Zenbleed, is a hardware use-after-free vulnerability in AMD Zen 2 processors caused by improper speculative handling of the vzeroupper instruction. Under specific microarchitectural circumstances, locally executing attacker-controlled code can expose sensitive data from memory associated with other processes, including privileged processes. The weakness affects the Zen 2 CPU architecture independently of the operating system and can undermine isolation boundaries involving processes, containers, sandboxes, and potentially virtual machines hosted on vulnerable hardware.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
LoongBleed is a local hardware vulnerability proof of concept for Loongson LA464 and LA664 processors with both LSX 128-bit SIMD and LASX 256-bit SIMD support. It tests whether narrow LSX or scalar floating-point operations leave stale data exposed in the upper portions of aliased 256-bit LASX $xr registers. The principal implementation, loongbleed_poc.cpp, is a multithreaded C++ program that uses inline LoongArch assembly to test 16 register slots ($xr0-$xr15), pins workers to CPUs, and supports vor, vld, fld.d, and fld.s trigger gadgets. It reports complete leaked register values and ASCII representations when non-zero data is found. The Rust implementation in src/main.rs is an alternate PoC that constructs the same gadget sequences as raw instruction encodings, places them in an RWX anonymous mmap page, executes them repeatedly, and reports unique results. run.sh builds and executes the C++ version. poc_la464.sh and poc_la664.sh create a local victim workload using numactl and sort to increase the likelihood of recovering predictable data; LA664 uses an SMT sibling, while LA464 uses the same CPU. The repository contains no network communication, command shell, persistence mechanism, or remote target functionality.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A moderate-severity local vulnerability covered by the TuxCare CentOS 7 local security-check advisory. The notice assigns CVSS 3.0 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N and states exploits are available.
A side-channel hardware information disclosure vulnerability in AMD Zen 2 processors caused by speculative execution behavior around the SIMD Zeroupper instruction, leaking stale register data.
An AMD hardware cross-process information-leak vulnerability addressed through the Red Hat Enterprise Linux 9 kernel-rt update.
AMD hardware vulnerability enabling cross-process information disclosure.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.