<div dir="ltr"><div><div style="font-size:small" class="gmail_default">DirtyFrag</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default"><a href="https://linux.slashdot.org/story/26/05/08/1913238/new-linux-dirty-frag-zero-day-gives-root-on-all-major-distros">https://linux.slashdot.org/story/26/05/08/1913238/new-linux-dirty-frag-zero-day-gives-root-on-all-major-distros</a></div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">This one does not have updates yet from the repositories.</div><div style="font-size:small" class="gmail_default">The patches are in the code, but not released yet.</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Someone watching the patches that are committed, figured out </div><div style="font-size:small" class="gmail_default">the exploit, and released it ahead of the updates. </div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">There is a mitigation here</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default"><a href="https://github.com/V4bel/dirtyfrag#mitigation">https://github.com/V4bel/dirtyfrag#mitigation</a></div></div><div><div style="font-size:small" class="gmail_default">As with this class of bugs, a local account is needed, so this is </div><div style="font-size:small" class="gmail_default">a concern if you have containers.</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">If you don&#39;t have containers, then the machine is not vulnerable.</div><br clear="all"></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Khalid M. Baheyeldin</div></div>