CVE-2025-23339 is a vulnerability in NVIDIA CUDA Toolkit affecting the cuobjdump utility on all platforms. The issue is a stack-based buffer overflow in cuobjdump's processing of malicious ELF input, with supporting reporting indicating the flaw is in DWARF parsing functionality. An attacker can trigger the vulnerability by convincing a user to run cuobjdump against a specially crafted ELF file. Successful exploitation can corrupt stack memory and result in arbitrary code execution in the context of the user executing cuobjdump.
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.
This repository contains three Python scripts (exploit_final_shell_working_final.py, exploit_v6.py, rop_oneshell2.py) that generate malicious ELF/CUBIN files designed to exploit CVE-2025-23339. The exploit targets a vulnerability in a binary (likely related to NVIDIA CUDA or similar) that processes CUBIN files. The scripts construct payloads using ROP chains or one_gadget techniques to achieve arbitrary code execution, typically spawning a shell via execve("/bin/sh"). The exploit requires knowledge of the target's memory layout (libc base, .bss section) and is intended for local exploitation, as it relies on the ability to supply crafted files to the vulnerable binary. No network endpoints or remote services are targeted. The repository is operational, providing working exploit scripts that generate the necessary payloads for exploitation.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.