I understand and agree with all of this, I&#x27;m just not sure how it follows from what I wrote.  The problem has a fix scheduled (what this submission is about), and in a fairly short period of time (~30 days for a fairly esoteric[1] bug).<p>To my mind there are two places to fix this, in the kernel for a real mitigation technique that helps &quot;solve&quot; the problem, and in the distros for quick fixes and hacks, or backports of the kernel fix, as necessary.  Systemd pushing a fix of their own 1) only affects distros using systemd, while this problem affects all recent distros that use efivarfs), 2) probably won&#x27;t get picked up by distros immediately excapt as a backported fix anyway, as I doubt most of them push new versions of something as integral as systemd every time a new version is out, at least not with a lot of testing, and 3) would not have been a good fix, and would have required the utilities that still needed access to actually remount a filesystem.<p>1: Triggering this problem is not as easy as what you (and I) wrote in most instances, as &#x2F; has special consideration in rm, and generally requires the &quot;--no-preserve-root&quot; flag.