More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2226595 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=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2226595,2238520 # 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
I'm closing this bug due to it not being exploitable on Fedora or RHEL. The bug in question is in code which reads COFF files. COFF is an object/executable format that is NOT used by Linux. Support for outputting this format was removed in GCC 8, which was last used in Fedora 29. A Fedora GDB user could attempt to load symbols from a COFF file brought in from some other OS, but, at worst, GDB would simply crash. While this is certainly a bug, it is definitely not a security concern. That said, since it is still a bug, albeit not a very important one, I have made a clone of this bug. See Bug 2238641.