Description of problem: When print-fatal-signals is enabled it's possible to dump any memory reachable by the kernel to the log by simply jumping to that address from user space. Or crash the system if there's some hardware with read side effects. The fatal signals handler will dump 16 bytes at the execution address, which is fully controlled by ring 3. In addition when something jumps to a unmapped address there will be up to 16 additional useless page faults, which might be potentially slow (and at least is not very efficient) Fortunately this option is off by default and only there on i386. But fix it by checking for kernel addresses and also stopping when there's a page fault. References: http://patchwork.kernel.org/patch/69752/ http://git.kernel.org/linus/b45c6e76bc2c72f6426c14bed64fdcbc9bf37cb0
print-fatal-signals is turned off by default in Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG.
kernel-2.6.30.10-105.2.4.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/kernel-2.6.30.10-105.2.4.fc11
kernel-2.6.30.10-105.2.4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2010:0147 https://rhn.redhat.com/errata/RHSA-2010-0147.html
This issue has been addressed in following products: Red Hat Enterprise Linux 4 Via RHSA-2010:0146 https://rhn.redhat.com/errata/RHSA-2010-0146.html
This issue has been addressed in following products: MRG for RHEL-5 Via RHSA-2010:0161 https://rhn.redhat.com/errata/RHSA-2010-0161.html