This bug has been copied from bug #310651 and has been proposed
to be backported to 4.6 z-stream (EUS).
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
Comment from Mark J.Cox:
After review we believe this actually doesn't qualify to be treated as a
The customers who reported this flaw have a non-default setup specifically
designed to cause a machine panic under OOM situations. The bug is likely to
trigger the panic under normal operating circumstances, even without a local
malicious attacker, and indeed this is how the reporting customers found this
So a local malicious attacker could cause the machine configured in this way to
panic (leaving their traces all over the audit log), but it was most likely
going to panic by itself at some point anyway.
I'm going to therefore remove the CVE name we allocated for this issue.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.