Incorrect conversion via row-stride multiplication overflow
Published May 16, 2025 · Updated Nov 3, 2025
Integer overflow in libavif before 1.3.0 allows local users to trigger incorrect row addressing during RGB-to-YUV conversion. The avifImageRGBToYUV function stores four row-byte values as uint32_t, so offset multiplications for very large image dimensions wrap before pointer arithmetic. The published 65536-by-65536 API test triggers an unsigned-overflow sanitizer check but reports no address-sanitizer memory error, leaving concrete data corruption or service interruption unproven.
Summary
What happened
Integer overflow in libavif before 1.3.0 allows local users to trigger incorrect row addressing during RGB-to-YUV conversion. The avifImageRGBToYUV function stores four row-byte values as uint32_t, so offset multiplications for very large image dimensions wrap before pointer arithmetic. The published 65536-by-65536 API test triggers an unsigned-overflow sanitizer check but reports no address-sanitizer memory error, leaving concrete data corruption or service interruption unproven.
The record
- CVE
- CVE-2025-48175
- Published
- May 16, 2025
- Updated
- Nov 3, 2025
- Vendor
- Alliance for Open Media
- Product
- libavif
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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 <1.3.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
- avifImageRGBToYUV 65536-by-65536 sanitizer proof of conceptproof 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