More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2277289 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.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2277289,2277290 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
*** This bug has been marked as a duplicate of bug 2277292 ***
FEDORA-2024-7a57842ec3 (gdcm-3.0.21-4.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7a57842ec3
FEDORA-2024-7a57842ec3 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7a57842ec3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7a57842ec3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-7a57842ec3 (gdcm-3.0.21-4.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.