More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2273404 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=2273404,2275855 # 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
FEDORA-2024-9be1b94714 (glibc-2.38-18.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9be1b94714
FEDORA-2024-f7ae5df88d (glibc-2.37-19.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f7ae5df88d
*** Bug 2275933 has been marked as a duplicate of this bug. ***
Still needs to be fixed in F40 and Rawhide. For F40 we will need a freeze exception because we want to deliver into the current freeze to fix the CVE.
The go/no-go meeting for Fedora 40 starts in 17 minutes, so including this would require a slip. I'm proposing it as a blocker per "The release must contain no known security bugs of 'important' or higher impact according to the Red Hat severity classification scale which cannot be satisfactorily resolved by a package update (e.g. issues during installation)." The Red Hat advisory for it - https://access.redhat.com/security/cve/CVE-2024-2961 - rates it as 'important'. The question is whether it can be "satisfactorily resolved by a package update", which basically boils down to, can this plausibly be exploited against a person doing the sort of things you might do from an installer environment or live desktop before installing and updating the system? Think normal client operations - browsing websites, that sort of thing. If it's only likely to be exploitable against *servers*, that's unlikely to be a blocker in my estimation.
(In reply to Adam Williamson from comment #6) > The go/no-go meeting for Fedora 40 starts in 17 minutes, so including this > would require a slip. I'm proposing it as a blocker per "The release must > contain no known security bugs of 'important' or higher impact according to > the Red Hat severity classification scale which cannot be satisfactorily > resolved by a package update (e.g. issues during installation)." The Red Hat > advisory for it - https://access.redhat.com/security/cve/CVE-2024-2961 - > rates it as 'important'. The question is whether it can be "satisfactorily > resolved by a package update", which basically boils down to, can this > plausibly be exploited against a person doing the sort of things you might > do from an installer environment or live desktop before installing and > updating the system? Think normal client operations - browsing websites, > that sort of thing. If it's only likely to be exploitable against *servers*, > that's unlikely to be a blocker in my estimation. The issue can be satisfactorily resolved by a glibc package update. I believe there is low exploit probability from someone doing things you might do from an installer e.g. normal client operations. It is much more likely to be exploitable against servers.
PR: https://src.fedoraproject.org/rpms/glibc/pull-request/94
Discussed during Fedora 40 Final go/no-go meeting #2: https://meetbot-raw.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.html . We agreed that, per Carlos' evaluation, this does not need to be fixed in the release candidate, but as it *is* a potential significant risk for servers, we want to ensure it is available as a day 0 update, so it is accepted as a 0-day blocker. This just means the update must be pushed stable by release day (2024-04-23).
FEDORA-2024-eafbf519ec (glibc-2.39-8.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-eafbf519ec
Fedora 40 fix is up now and will be part of the 0day fix for the release. Fedora Rawhide will be fixed next.
FEDORA-2024-9be1b94714 has been pushed to the Fedora 39 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-9be1b94714` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9be1b94714 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-eafbf519ec has been pushed to the Fedora 40 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-eafbf519ec` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-eafbf519ec See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f7ae5df88d 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-f7ae5df88d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f7ae5df88d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
The plan is to fix Rawhide on Monday (2024-04-22) when we do our weekly CI/CD from upstream.
FEDORA-2024-eafbf519ec (glibc-2.39-8.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
F40 update being pushed stable resolves the F40 0-day blocker status, so dropping those tags.
FEDORA-2024-9be1b94714 (glibc-2.38-18.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-f7ae5df88d (glibc-2.37-19.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.