Bug 2496908

Summary:	CVE-2026-58379 gimp: gimp: Heap buffer overflow in read_channel_data() [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Rafael Pandini <rpandini>
Component:	gimp	Assignee:	Nils Philippsen <nphilipp>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	45	CC:	jridky, nphilipp, phracek, zdohnal
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---	Flags:	fedora-admin-xmlrpc: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["1295a07a-cd00-4197-b26a-bea7fac317c5"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rafael Pandini 2026-07-03 18:11:10 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A heap buffer overflow write vulnerability exists in GIMP's Paint Shop Pro (PSP) file format parser. In read_channel_data() in file-psp.c, for low bit-depth images (depth=1 or 4), line_width uses a packed formula (8 pixels/byte) but fread() reads width bytes (1 byte/pixel). For example, with width=33 and depth=1: allocates 4 bytes, writes 33 — a 29-byte heap overflow.

This is a variant of CVE-2026-4153 (commit 98cb1371), which fixed read_layer_block() but left the buf allocation in read_channel_data() unpatched.

- Function: read_channel_data()
- File: plug-ins/common/file-psp.c:1558-1784
- Fix: https://gitlab.gnome.org/GNOME/gimp/-/commit/b630f167
- Hardening: https://gitlab.gnome.org/GNOME/gimp/-/commit/20b00d6d
- Upstream issue: https://gitlab.gnome.org/GNOME/gimp/-/issues/16205
- Acknowledgment: bb1abu

Comment 1 Aoife Moloney 2026-08-17 15:14:11 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.