This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate.
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=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1820331,1820332 # 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 is blocked on acceptance of a fix upstream.
This is still waiting on upstream bug fix. However, we now have a proposed fix that is being discussed upstream: https://sourceware.org/pipermail/libc-alpha/2020-April/112671.html
v2 for review: https://sourceware.org/pipermail/libc-alpha/2020-April/112747.html
Updated patch from Huawei has been posted: https://patchwork.sourceware.org/project/glibc/patch/ac494a6febda4430857df1fc31f64e19@huawei.com/
The actual fixes are: commit beea361050728138b82c57dda0c4810402d342b9 Author: Alexander Anisimov <a.anisimov> Date: Wed Jul 8 14:18:31 2020 +0200 arm: CVE-2020-6096: Fix multiarch memcpy for negative length [BZ #25620] Unsigned branch instructions could be used for r2 to fix the wrong behavior when a negative length is passed to memcpy. This commit fixes the armv7 version. commit 79a4fa341b8a89cb03f84564fd72abaa1a2db394 Author: Evgeny Eremin <e.eremin> Date: Wed Jul 8 14:18:19 2020 +0200 arm: CVE-2020-6096: fix memcpy and memmove for negative length [BZ #25620] Unsigned branch instructions could be used for r2 to fix the wrong behavior when a negative length is passed to memcpy and memmove. This commit fixes the generic arm implementation of memcpy amd memmove. Plus the NEWS file update (still pending upstream). Backporting the new test is more complicated because of its dependency on support/ directory changes, so this should be considered optional.
FEDORA-2020-4e92a61688 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4e92a61688
FEDORA-2020-4e92a61688 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4e92a61688` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4e92a61688 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-4e92a61688 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.