The fixes for this are as follows, details here (https://bugzilla.redhat.com/show_bug.cgi?id=1198109)

- 759496ba ("arch: mm: pass userspace fault flag to generic fault handler")
- 3a13c4d7 ("x86: finish user fault error path with fatal signal")
- 519e5247 ("mm: memcg: enable memcg OOM killer only for user faults")
- fb2a6fc5 ("mm: memcg: rework and document OOM waiting and wakeup")
- 3812c8c8 ("mm: memcg: do not trap chargers with full callstack on OOM")
- 49426420 ("mm: memcg: handle non-error OOM situations more gracefully")
- 84235de3 ("fs: buffer: move allocation failure loop into the allocator")
- a0d8b00a ("mm: memcg: do not declare OOM from __GFP_NOFAIL allocations")
- 1f14c1ac ("mm: memcg: do not allow task about to OOM kill to bypass the limit")
- 3168ecbe ("mm: memcg: use proper memcg in limit bypass")

These patches are present on 4.14, 4.4, 3.18, 3.14.
These patches are not found on 3.10, 3.8.

1 other patch which is related but does not necessarily have to be applied.
- 0772dac1dc2 ("arch/parisc/mm/fault.c: fix uninitialized variable usage")

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Per our CVE severity guidelines, this does not block stable releases. Also, there is nothing to revert, other than the decision to use the Linux kernel. Updating priority and impact per guidelines. Dropping ReleaseBlock. sheriffbot, please remain silent.

Let's downgrade to severity low since this is just a DoS and hard to exploit on Chrome OS. That should calm down sheriffbot :)

The patches do not cleanly apply on the older kernels. Given the severity, it might be better to not apply these patches in favor of ease of maintenance over the longer term. Closing this bug as WontFix.