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=1847608,1847609 # 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 was fixed in rawhide with the recent rebase to bison-3.6.4 (bug 1792738). In total, there were five reported failures, generated by a fuzzer: https://lists.gnu.org/archive/html/bug-bison/2020-03/msg00006.html https://lists.gnu.org/archive/html/bug-bison/2020-03/msg00007.html https://lists.gnu.org/archive/html/bug-bison/2020-03/msg00008.html https://lists.gnu.org/archive/html/bug-bison/2020-03/msg00009.html https://lists.gnu.org/archive/html/bug-bison/2020-03/msg00010.html I have tested that bison-3.6.4-1.fc33 gracefully errors out on all of these, instead of crashing like they were before the fixes. Considering that typically, running bison is a build-time activity and the input is essentially code, a bison crash is going to cause a build to fail; and since all of these inputs are broken files generated by a fuzzer, this doesn't have a significant impact. Therefore, for now, we won't backport this to F31 or F32. However, the upcoming F33 will have this fix.