A flaw was found in GIMP when processing XCF image files. If a user opens one of these image files that has been specially crafted by an attacker, GIMP can be tricked into making serious memory errors, potentially leading to crashes and causing use-after-free issues.
Workaround:
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2025:9162 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9165 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9308 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9309 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9310 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9314 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9315 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9316 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9501 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2025:9569 | vendor advisory |
| https://access.redhat.com/security/cve/CVE-2025-48798 | vdb entry |
| https://bugzilla.redhat.com/show_bug.cgi?id=2368557 | issue tracking |