Bug 2391817 - CVE-2025-54080 exiv2: Exiv2 Segmentation Faults [fedora-42]
Summary: CVE-2025-54080 exiv2: Exiv2 Segmentation Faults [fedora-42]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: exiv2
Version: 42
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Steve Cossette
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["1abda673-b69b-420f-95d5-d...
Depends On:
Blocks: CVE-2025-54080
TreeView+ depends on / blocked
 
Reported: 2025-08-29 16:33 UTC by Jon Moroney
Modified: 2025-09-16 00:18 UTC (History)
2 users (show)

Fixed In Version: exiv2-0.28.6-2.fc42 exiv2-0.28.6-2.fc43
Clone Of:
Environment:
Last Closed: 2025-09-01 00:50:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Moroney 2025-08-29 16:33:28 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.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Fedora Update System 2025-08-29 20:42:39 UTC
FEDORA-2025-1edba49b51 (exiv2-0.28.6-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1edba49b51

Comment 2 Fedora Update System 2025-08-29 20:43:31 UTC
FEDORA-2025-49cb471dc1 (exiv2-0.28.6-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-49cb471dc1

Comment 3 Fedora Update System 2025-08-30 01:11:35 UTC
FEDORA-2025-1edba49b51 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1edba49b51`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1edba49b51

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

Comment 4 Fedora Update System 2025-08-30 02:01:52 UTC
FEDORA-2025-49cb471dc1 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-49cb471dc1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-49cb471dc1

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

Comment 5 Fedora Update System 2025-08-31 01:35:48 UTC
FEDORA-2025-c23727e694 (exiv2-0.28.6-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c23727e694

Comment 6 Fedora Update System 2025-08-31 01:36:52 UTC
FEDORA-2025-387e64c9fd (exiv2-0.28.6-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-387e64c9fd

Comment 7 Fedora Update System 2025-09-01 00:50:53 UTC
FEDORA-2025-387e64c9fd (exiv2-0.28.6-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-09-01 02:09:13 UTC
FEDORA-2025-c23727e694 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c23727e694`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c23727e694

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

Comment 9 Fedora Update System 2025-09-16 00:18:56 UTC
FEDORA-2025-c23727e694 (exiv2-0.28.6-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.