Bug 2369868
| Summary: | CVE-2025-5455 qt5-qtbase: QtCore Assertion Failure Denial of Service [fedora-41] | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jon Moroney <jmoroney> |
| Component: | qt5-qtbase | Assignee: | Than Ngo <than> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 41 | CC: | jgrulich, kde-sig, mfindra, rdieter, than |
| Target Milestone: | --- | Keywords: | Security, SecurityTracking |
| Target Release: | --- | Flags: | than:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | {"flaws": ["18af4671-b7b4-4f85-8a93-08af4cf17199"]} | ||
| Fixed In Version: | qt5-qtbase-5.15.17-2.fc41 qt5-qtbase-5.15.17-2.el10_2 qt5-qtbase-5.15.17-2.fc42 qt5-qtbase-5.15.17-6.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-10-28 01:45: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: | 2369722 | ||
|
Description
Jon Moroney
2025-06-02 19:10:46 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. Working on it FEDORA-2025-c50e4dfd3b (qt5-qtbase-5.15.17-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c50e4dfd3b FEDORA-2025-26e2e0c477 (qt5-qtbase-5.15.17-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-26e2e0c477 FEDORA-2025-9a46af550f 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-9a46af550f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9a46af550f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-fd412e2ace has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fd412e2ace See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-c50e4dfd3b 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-c50e4dfd3b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c50e4dfd3b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-26e2e0c477 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-26e2e0c477` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-26e2e0c477 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-26e2e0c477 (qt5-qtbase-5.15.17-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-fd412e2ace (qt5-qtbase-5.15.17-2.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-c50e4dfd3b (qt5-qtbase-5.15.17-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-9a46af550f (qt5-qtbase-5.15.17-6.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |