Bug 2366410

Summary:	CVE-2025-4638 zsync: Improper Pointer Arithmetic in pcl [epel-9]
Product:	[Fedora] Fedora EPEL	Reporter:	Avinash Hanwate <ahanwate>
Component:	zsync	Assignee:	Tobias <t-fedora>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	epel9	CC:	t-fedora
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["ddd8b347-24b4-435f-801a-403d892f961e"]}
Fixed In Version:	zsync-0.6.2-3.el9	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-05-23 02:50:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2366317

Description Avinash Hanwate 2025-05-15 06:10:05 UTC

More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2366317

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.

Comment 1 Fedora Update System 2025-05-15 18:42:02 UTC

FEDORA-EPEL-2025-f708ea631b (zsync-0.6.2-3.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f708ea631b

Comment 2 Fedora Update System 2025-05-16 00:21:15 UTC

FEDORA-EPEL-2025-f708ea631b has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f708ea631b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2025-05-23 02:50:21 UTC

FEDORA-EPEL-2025-f708ea631b (zsync-0.6.2-3.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.