Description of problem: Exim produces sigfaults ( see below ) . I have check three events with the mainlog and not one event seems similar to eachother. The Problem maps at least back before the 10.2. . It started at 11:45 CET. Nothing new got installed on the 10th of Feburary at or before this time. No clue what it's causing. Could be an attack attempt of some sort. Version-Release number of selected component (if applicable): 4.84-4 Additional info: Mar 11 13:45:00 s36 kernel: [ 211.111743] exim[3948]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:54:23 s36 kernel: [ 774.162207] exim[13199]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:54:23 s36 kernel: exim[13199]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:55:01 s36 kernel: [ 811.917703] exim[13524]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:55:01 s36 kernel: exim[13524]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:56:02 s36 kernel: [ 872.652687] exim[16159]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:56:02 s36 kernel: exim[16159]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:57:01 s36 kernel: [ 931.681357] exim[16734]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 13:57:01 s36 kernel: exim[16734]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:05:02 s36 kernel: [ 1412.874891] exim[23611]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:05:02 s36 kernel: exim[23611]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:07:51 s36 kernel: [ 1582.158468] exim[27476]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:07:51 s36 kernel: exim[27476]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:08:46 s36 kernel: [ 1636.733814] exim[28176]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:08:46 s36 kernel: exim[28176]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:14:09 s36 kernel: [ 1960.248858] exim[663]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:14:09 s36 kernel: exim[663]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:15:03 s36 kernel: [ 2013.553811] exim[2150]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:15:03 s36 kernel: exim[2150]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:22:50 s36 kernel: [ 2481.257786] exim[10038]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:22:50 s36 kernel: exim[10038]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:24:06 s36 kernel: [ 2557.029639] exim[10680]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:24:06 s36 kernel: exim[10680]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:25:04 s36 kernel: [ 2614.407384] exim[12331]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:25:04 s36 kernel: exim[12331]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:25:36 s36 kernel: [ 2646.612916] exim[13196]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:25:36 s36 kernel: exim[13196]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:29:08 s36 kernel: [ 2858.453590] exim[15232]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:29:08 s36 kernel: exim[15232]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:35:05 s36 kernel: [ 3215.615426] exim[22299]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:35:05 s36 kernel: exim[22299]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:40:52 s36 kernel: [ 3563.206414] exim[28587]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:40:52 s36 kernel: exim[28587]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:41:12 s36 kernel: [ 3582.810356] exim[28829]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:41:12 s36 kernel: exim[28829]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:45:06 s36 kernel: [ 3816.528815] exim[352]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:45:06 s36 kernel: exim[352]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:47:25 s36 kernel: [ 3956.222177] exim[2421]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:47:25 s36 kernel: exim[2421]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:55:06 s36 kernel: [ 4417.244660] exim[10909]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:55:06 s36 kernel: exim[10909]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:58:41 s36 kernel: [ 4632.172463] exim[13404]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:58:41 s36 kernel: exim[13404]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:59:14 s36 kernel: [ 4665.139384] exim[13769]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Mar 11 14:59:14 s36 kernel: exim[13769]: segfault at 0 ip b76e08e7 sp bff8c6f0 error 6 in exim[b763b000+11b000] Exim Mainlog for a few events: 2015-03-09 14:55:06 1YUy9C-00014v-05 H=mout.kundenserver.de [212.227.126.130] Warning: send for >EMAILADDRESS< 2015-03-09 14:58:41 no host name found for IP address 190.255.210.11 2015-03-08 14:59:14 H=laubervilliers-656-1-236-113.w193-248.abo.wanadoo.fr [193.248.33.113] F=<eruptionvv1osd> rejected RCPT <>EMAILADDRESS<>: you have been blacklisted. 2015-03-09 14:59:14 H=host71-87-static.107-82-b.business.telecomitalia.it (alicegate.homenet.telecomitalia.it) [82.107.87.71] F=<paul> rejected RCPT <>EMAILADDRESS<>: you have been blacklisted. 2015-03-11 14:59:14 1YVhAF-0003Z6-0O SMTP error from remote mail server after RCPT TO:<xteam>: host mx.t-online.hu [84.2.46.11]: 451 4.2.0 <>EMAILADDRESS<>: Recipient address rejected: You are greylisted for 600 seconds (see http://cgi.t-online.hu/bra02/mxtest.cgi?err=GRYLST for details) 2015-03-11 14:59:14 1YVhAH-0003Zk-L5 => /mailacct/joymacommail10/Maildir/ (>EMAILADDRESS<) <>EMAILADDRESS<> R=virtual_user T=address_directory 2015-03-11 14:59:14 1YVhAH-0003Zk-L5 Completed
- the ip is not running on the system. - the ip is invalid in term of read left to right - read from right to left, it's a multicast ip. - server does not get multicasts or tcpdump isn't showing them.
This does not look like an attack to me. The EIP and ESP are always the same in all crashes, so it looks like something is retrying to send the same data over and over. Perhaps capturing the traffic to the server that leads to these segfaults would be a good step forward in understanding these crashes. I'll remove the Security keyword now and let's treat this as a normal bug in Fedora. Please work with the exim maintainer to get help.
This is being tracked in upstream bug tracker as http://bugs.exim.org/show_bug.cgi?id=1601 It is highly likely related to http://bugs.exim.org/show_bug.cgi?id=1558 which is already fixed and will be in next release. OP has not responded to comments on that bug, it'd be helpful if they could.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.