Using mail-mta/exim-4.97.1-r6, email delivery attempts to a me.com email address would cause exim to segv and freeze the email. Updating to mail-mta/exim-4.98 delivers the same email successfully. Reproducible: Always Steps to Reproduce: 1. See frozen email to me.com address 2. exim -M <email-id> 3. Observe exim panic messages with old version Actual Results: With mail-mta/exim-4.97.1-r6: # tail -n 21 exim_panic.log 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 SIGSEGV (fault address: 0x17c) 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 SEGV_MAPERR 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 SIGSEGV (null pointer indirection) 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 SIGSEGV (19952 delivering 1tWBuX-000000007HQ-2Ac0 to mx02.mail.icloud.com [17.57.156.30] (<user>@me.com) ) 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 backtrace 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 --- 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(stackdump+0x38) [0x564a6e34d6e8] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(+0x4c8b4) [0x564a6e34d8b4] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 /lib64/libc.so.6(+0x3c160) [0x7f0d5d612160] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(smtp_transport_entry+0xf15) [0x564a6e3ed9e5] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(+0x409f3) [0x564a6e3419f3] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(deliver_message+0x2678) [0x564a6e346eb8] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(main+0x467c) [0x564a6e32717c] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 /lib64/libc.so.6(+0x26200) [0x7f0d5d5fc200] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 /lib64/libc.so.6(__libc_start_main+0x89) [0x7f0d5d5fc2b9] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 exim(_start+0x25) [0x564a6e32a585] 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 --- 2025-01-11 16:40:39 1tWBuX-000000007HQ-2Ac0 Delivery status for <user>@me.com: got 0 of 7 bytes (pipeheader) from transport process 19952 for transport smtp Expected Results: Successful delivery with no panic. I see mail-mta/exim-4.98 is masked due to other issues, but I need it to solve this problem, and have unmasked it.
Created attachment 916333 [details] emerge --info Emerge --info after upgrading exim to 4.98.
Looking at the exim_main.log after the update I see that proofpoint is blocking my ip address, even so, exim should not segv.
:(
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f99d3ec97d00fbf7938720e294e3a40b54e76a3 commit 1f99d3ec97d00fbf7938720e294e3a40b54e76a3 Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2025-04-05 08:35:59 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2025-04-05 08:37:35 +0000 mail-mta/exim-4.98.2: version bump (CVE-2025-30232) Bug: https://bugs.gentoo.org/952139 Bug: https://bugs.gentoo.org/947916 Signed-off-by: Fabian Groffen <grobian@gentoo.org> mail-mta/exim/Manifest | 2 ++ mail-mta/exim/{exim-4.98.ebuild => exim-4.98.2.ebuild} | 3 ++- mail-mta/exim/files/exim-4.98-tidydb-crash.patch | 16 ++++++++++++++++ 3 files changed, 20 insertions(+), 1 deletion(-)
