QCOW image corruption via wrapped L1 length
Published Jun 25, 2025 · Updated Jun 25, 2025
Integer overflow in qCUDA at commit db0085400c2f2011eed46fbc04fdc0873141688e allows local users to corrupt a QCOW image. In qcow_make_empty in qcu-device/block/qcow.c, a 32-bit multiplication of s->l1_size by eight wraps and supplies a truncated length to bdrv_truncate(). Low-privileged local access is required; a sufficiently large L1 table can truncate the image at its L1 table offset rather than its valid end.
Summary
What happened
Integer overflow in qCUDA at commit db0085400c2f2011eed46fbc04fdc0873141688e allows local users to corrupt a QCOW image. In qcow_make_empty in qcu-device/block/qcow.c, a 32-bit multiplication of s->l1_size by eight wraps and supplies a truncated length to bdrv_truncate(). Low-privileged local access is required; a sufficiently large L1 table can truncate the image at its L1 table offset rather than its valid end.
The record
- CVE
- CVE-2025-6603
- Published
- Jun 25, 2025
- Updated
- Jun 25, 2025
- Vendor
- coldfunction
- Product
- qCUDA
- Classifications
- CWE-189, CWE-190, T1485
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2025CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=db0085400c2f2011eed46fbc04fdc0873141688e
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
No public exploit references are available in this record.
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