Medium [CVE-2026-70654] Heap buffer overflow allows memory corruption and denial of service.
This medium-severity Red Hat Linux advisory covers CVE-2026-70654.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
libvips is a fast image processing library with low memory needs. Prior to version 8.18.3, applications that define unusual custom libvips sources and use them to process untrusted uncompressed PPM images can trigger a max/min error in vips_source_read_to_memory in libvips/iofuncs/source.c.
The function uses VIPS_MAX instead of VIPS_MIN when selecting the remaining read size, allowing up to 4032 bytes to be written beyond the allocated heap buffer and causing memory corruption or a process crash. This issue is fixed in version 8.18.3.
This vulnerability, located in the vips_source_read_to_memory function, allows a local attacker to write beyond an allocated memory buffer. This can lead to memory corruption or cause the application to crash, resulting in a denial of service.
This Moderate impact flaw in libvips involves a heap buffer overflow when processing untrusted uncompressed PPM images through applications configured with unusual custom libvips sources. Exploitation requires a specific, non-default application setup and user interaction, which reduces the overall risk in typical Red Hat environments.
Red Hat severity: Moderate — CVSS 4.4 (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H). Weakness: CWE-787.
- < 8.18.3
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation
Upgrade to a fixed release: 8.18.3. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.