Bug 2521147

Summary:	CVE-2025-68114 rust: Capstone: Memory corruption via unchecked vsnprintf return [fedora-43]
Product:	[Fedora] Fedora	Reporter:	Praise Ogwuche <pogwuche>
Component:	rust	Assignee:	Rust SIG <rust-sig>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	43	CC:	amulhern, igor.raits, jchecahi, jistone, paumurph, rust-sig
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["18ccc59d-83a6-4a40-84de-34ab619140cc"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-08-21 20:45:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2423416

Description Praise Ogwuche 2026-08-21 19:53:29 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Capstone is a disassembly framework. In versions 6.0.0-Alpha5 and prior, an unchecked vsnprintf return in SStream_concat lets a malicious cs_opt_mem.vsnprintf drive SStream’s index negative or past the end, leading to a stack buffer underflow/overflow when the next write occurs. Commit 2c7797182a1618be12017d7d41e0b6581d5d529e fixes the issue.

Comment 1 Paul Murphy 2026-08-21 20:45:13 UTC

capstone is not used nor built by the rust package.

@pogwuche in more recent updates to rust packaging, the capstone source included with the original rust source, but is removed during the prep stage. Do you know if that is sufficient to prevent reporting false positives?

Comment 2 Praise Ogwuche 2026-08-21 22:10:33 UTC

Yes. If is is removed during the prep stage and the final package doesn’t build or ship capstone, that’s sufficient. we’d set as not affected on our end going forward(if it happens to appear in our manifest).