More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2240246 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=2240246,2240553 # 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
Is this CVE even relevant for Fedora? According to upstream, the fix was introduced in version 10.5.17 and we have 10.5.21 (for a few days 10.5.22) in Fedora.
Apologies the 10.5.22 is only in Rawhide, however, the 10.5.21 is present in F38 (even in F37) as well.
This CVE is fixed by upstream in MariaDB 10.5.17, as per: https://mariadb.com/kb/en/security/ We already have far newer version in Fedora - 10.5.21 https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2023-c6de09b579