Bug 2354002 - CVE-2025-2581 xmedcon: xmedcon DICOM File malloc integer underflow [fedora-41]
Summary: CVE-2025-2581 xmedcon: xmedcon DICOM File malloc integer underflow [fedora-41]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xmedcon
Version: 41
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["80309093-44a2-429f-9664-c...
Depends On:
Blocks: CVE-2025-2581
TreeView+ depends on / blocked
 
Reported: 2025-03-21 06:57 UTC by Michal Findra
Modified: 2025-11-17 03:35 UTC (History)
1 user (show)

Fixed In Version: xmedcon-0.25.3-1.fc43 xmedcon-0.25.3-1.fc42 xmedcon-0.25.3-1.fc41
Clone Of:
Environment:
Last Closed: 2025-11-17 02:44:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Findra 2025-03-21 06:57:45 UTC
More information about this security flaw is available in the following bug:

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

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-11-08 21:03:11 UTC
FEDORA-2025-977a26e133 (xmedcon-0.25.3-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-977a26e133

Comment 2 Fedora Update System 2025-11-08 21:03:19 UTC
FEDORA-2025-9d4a8ab586 (xmedcon-0.25.3-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-9d4a8ab586

Comment 3 Fedora Update System 2025-11-08 21:03:28 UTC
FEDORA-2025-805b8f571a (xmedcon-0.25.3-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-805b8f571a

Comment 4 Fedora Update System 2025-11-09 03:53:19 UTC
FEDORA-2025-977a26e133 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-977a26e133`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-977a26e133

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

Comment 5 Fedora Update System 2025-11-09 04:35:58 UTC
FEDORA-2025-805b8f571a 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-805b8f571a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-805b8f571a

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

Comment 6 Fedora Update System 2025-11-09 05:01:20 UTC
FEDORA-2025-9d4a8ab586 has been pushed to the Fedora 41 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-9d4a8ab586`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9d4a8ab586

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

Comment 7 Fedora Update System 2025-11-17 02:44:28 UTC
FEDORA-2025-977a26e133 (xmedcon-0.25.3-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-11-17 02:59:18 UTC
FEDORA-2025-805b8f571a (xmedcon-0.25.3-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-11-17 03:35:57 UTC
FEDORA-2025-9d4a8ab586 (xmedcon-0.25.3-1.fc41) has been pushed to the Fedora 41 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.