###REGRESSION### -> worked in 4.96.x Bugtracker ( Bugzilla does not accept it for some bizzare reason ) https://bugs.exim.org/show_bug.cgi?id=3047 Description of problem: exim 4.97.1 introduced a new bug on all fedora/redhat production systems upgrading from 4.96 to 4.97. According to exim devs, pcre2 miscalculates something to -16 and tries to alloc it. 2024-01-21 00:36:09 1rRKsd-00000006BkG-0P8F bad internal_store_malloc request (2147483632 bytes) from function_store_get 66 Sounds like a 32 bit unsigned int issue to me, as pcre2 does not detect that it calculated a -16. Note: do not switch the component to pcre2, but pls add the maintainers from pcre packages to this bug. Exim is broken on production systems, but we need to fix exim now, and can't wait for pcre2 to debug this. @Pcre2 maintainers: pls provide a bug to the pcre2 bugtracker for this issue, they need to check, why they try to alloc 2 GB of memory, when they should not alloc memory at all due to negatives sizes. If the Exim devs are correct, this is a major bug in the lib. Version-Release number of selected component (if applicable): 4.97.0+ How reproducible: 100% reliable Steps to Reproduce: Send yourself a message with > 5 MB , i.e. 5 images from your phone.
Additional note: AFAIK the bug needs a config that utilizes pcre functionality i.e. regexp , which is very common, but may not be part of the default config shipped with exim. The most used regexp will the 0-day prevention rule from 2020 to filter out the "run{}" root-exploit.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
FEDORA-2024-c4c5481a1c (exim-4.97.1-5.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c4c5481a1c
FEDORA-2024-c4c5481a1c (exim-4.97.1-5.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Ähm.. yes. As you did not release a version for F38/39 , the issue still persists there. The bugreport was opened against Rawhide, as all version where affected.
Indeed, the f39/f40 versions are built; not yet tested locally and pushed as an update. I'll do f38 too.
thx
FEDORA-2024-0f5e4879fd (exim-4.97.1-5.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0f5e4879fd
FEDORA-2024-050c0b0b44 (exim-4.97.1-5.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-050c0b0b44
FEDORA-2024-f3fb15da40 (exim-4.97.1-5.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f3fb15da40
While Updateing: Ausgeführtes Scriptlet: exim-clamav-4.97.1-5.fc38.x86_64 2/6 /bin/chown: warning: '.' should be ':': „exim.exim“ And after the server restart, a message from January war delivered.. that's strange.. in a positive way :D it's a 20 MB mail, which had hit the the 2 MB limit issue in 4.97.1-1 and is now deliverable. OP SUCCESS! :D
> /bin/chown: warning: '.' should be ':': „exim.exim“ Fixed that one in rawhide but unless it's actually causing a problem, there's probably no need to backport it until/unless there's another bugfix update for earlier releases? Thanks for testing.
I agree on, that it's not urgent, in special for f38. AFAIK it's planned to change the behavior of chown in the medium future. Waiting too long, will create unnecessary issues in the future ;) In the end, it's just a simple replace in the specfiles. Not worth waiting in a queue for years.
FEDORA-2024-050c0b0b44 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-050c0b0b44` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-050c0b0b44 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0f5e4879fd 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-0f5e4879fd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0f5e4879fd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f3fb15da40 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-f3fb15da40` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f3fb15da40 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-050c0b0b44 (exim-4.97.1-5.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-f3fb15da40 (exim-4.97.1-5.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-0f5e4879fd (exim-4.97.1-5.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.