Loading vulnerability…
NVIDIA CUDA Toolkit contains a vulnerability in the cuobjdump binary affecting ELF section parsing. According to the provided content, the flaw in cuobjdump 12.8.55 is an integer overflow caused by failure to properly validate buffer length while processing a specially crafted ELF/fatbin file. This can result in an out-of-bounds write during parsing. An attacker who can supply a malformed file to the tool may trigger a crash or achieve arbitrary code execution.
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 is a proof-of-concept (PoC) exploit for CVE-2025-23247, a vulnerability in NVIDIA's cuobjdump utility (see TALOS-2025-2151). The exploit demonstrates the ability to control a buffer and offset in cuobjdump by crafting a CUDA cubin file with a malicious .nv_debug_source ELF section. The main file, modify_simple.c, takes an input cubin file and appends a specially crafted section that triggers an integer overflow and buffer manipulation when processed by cuobjdump, resulting in a crash and demonstrating an arbitrary address write primitive. The repository also includes a simple CUDA kernel (simple.cu) for generating a base cubin file. The exploit is local and requires the attacker to supply a malicious file to the vulnerable utility. No network endpoints are involved; all fingerprintable endpoints are file paths and ELF section names. The code is a PoC and does not provide a weaponized payload, but it clearly demonstrates exploitability and control over the vulnerable code path.
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.