Local service interruption via zero-sized allocation
Published May 24, 2025 · Updated May 24, 2025
Memory-safety flaw in spiral-rs within Blyss SDK 0.2.0 allows attackers to trigger undefined behavior through a zero-length allocation. AlignedMemory64::new multiplies its element count by eight and passes the resulting zero-byte Layout to alloc_zeroed without rejecting zero. Reachability requires consuming code to call the constructor with zero; the CNA assessment limits the reported impact to reduced availability.
Summary
What happened
Memory-safety flaw in spiral-rs within Blyss SDK 0.2.0 allows attackers to trigger undefined behavior through a zero-length allocation. AlignedMemory64::new multiplies its element count by eight and passes the resulting zero-byte Layout to alloc_zeroed without rejecting zero. Reachability requires consuming code to call the constructor with zero; the CNA assessment limits the reported impact to reduced availability.
The record
- CVE
- CVE-2025-48755
- Published
- May 24, 2025
- Updated
- May 24, 2025
- Vendor
- Blyss
- Product
- Blyss SDK
- Classifications
- CWE-762, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2025CVE publishedPublication date reported by the CVE source.
- May 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- AlignedMemory64 zero-size Miri reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo