[CLSA-2026:1788774195] gimp: Fix of 7 CVEs
Type:
security
Severity:
Important
Release date:
2026-09-07 09:43:31 UTC
Description:
- CVE-2026-18301: validate the PSD channel data allocation with a checked multiplication and fail cleanly instead of overflowing the raw_data buffer - CVE-2026-18302: pass the correct row stride to convert_int2uint() when loading separate-plane TIFFs so the conversion cannot write past the end of the heap-allocated row buffer - CVE-2026-18303: reject indexed TIFFs whose bit depth implies a color map larger than 256 entries instead of overrunning the 768-byte stack cmap - CVE-2026-18304: compute the TIFF upscale tile area as gsize and use a checked allocation so an integer overflow cannot undersize bw_buffer - CVE-2026-18305: use checked multiplications for the TIFF RGBA image allocation instead of an overflowing width times height product - CVE-2026-18306: reject SGI files whose bits-per-pixel is outside the supported range of 1 to 2 and cast the SGI row pointer arithmetic to gsize so an integer overflow cannot lead to an out-of-bounds write - CVE-2026-18307: derive the TIFF bytes-per-pixel consistency check from the source babl format so a samples-per-pixel below the photometric setting cannot undercount the buffer size, and size the contiguous tile buffer with checked multiplications instead of trusting TIFFTileSize()
Updated packages:
  • gimp-2.99.8-4.el9.2.tuxcare.els19.x86_64.rpm
    sha:9848fc191f854ac621c9a877c32d34128ee50d537c16ec58da1593dbe30d716f
  • gimp-devel-2.99.8-4.el9.2.tuxcare.els19.x86_64.rpm
    sha:89c4ffa51a4d5d9ad9cdcdf9c17cf7d8cfb963ebf4daad9e9c64b3b5b3f75277
  • gimp-devel-tools-2.99.8-4.el9.2.tuxcare.els19.x86_64.rpm
    sha:9bd62e26b3799fa1a841286a0640f759d9bcb679999c340cb8ee2bde27cb666f
  • gimp-libs-2.99.8-4.el9.2.tuxcare.els19.i686.rpm
    sha:7b5d4dd0c366d18c320ce2ce93c6e76d7bb88f2771ff71af4989a40418e8fb17
  • gimp-libs-2.99.8-4.el9.2.tuxcare.els19.x86_64.rpm
    sha:a963c250fe14a5c345fd395005495baae80c46f792be49917183aec25d90366f
Notes:
This page is generated automatically and has not been checked for errors. For clarification or corrections please contact the CloudLinux Packaging Team.