Bug 2361341 - CVE-2025-43963 digikam: out-of-buffer access [fedora-41]
Summary: CVE-2025-43963 digikam: out-of-buffer access [fedora-41]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: digikam
Version: 41
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["13b7291e-cd4b-4841-afba-1...
Depends On:
Blocks: CVE-2025-43963
TreeView+ depends on / blocked
 
Reported: 2025-04-21 04:25 UTC by Avinash Hanwate
Modified: 2025-04-30 01:37 UTC (History)
4 users (show)

Fixed In Version: digikam-8.6.0-4.fc41
Clone Of:
Environment:
Last Closed: 2025-04-30 01:37:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2025-04-21 04:25:47 UTC
More information about this security flaw is available in the following bug:

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

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-04-21 22:13:52 UTC
FEDORA-2025-5bbbb2df79 (digikam-8.6.0-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5bbbb2df79

Comment 2 Fedora Update System 2025-04-22 01:55:53 UTC
FEDORA-2025-5bbbb2df79 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-5bbbb2df79`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5bbbb2df79

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

Comment 3 Fedora Update System 2025-04-30 01:37:58 UTC
FEDORA-2025-5bbbb2df79 (digikam-8.6.0-4.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.