You have missed the point. Back up and look at the problem at a basic level. Your kernel can only leak shared memory to software running on your local machine, right? So there is no harm in being of control of the code that is executing on your local machine. Browser script control in no way mitigates the actual bug, but if you can limit the untrusted 3rd party code running in your browser, you could reduce your risk exposure, right? So if you have verified that all local code is signed and trusted, that is not the adversary that is potentially going to read your memory and exfiltrate your data. The main remaining risk is the scripts (code) that run in your browser, particularly the 3rd party kind. The Firefox fix was only a partial mitigation to the problem, and I have not seen a release yet for Chrome. Regardless, it will require a PC firmware fix to completely mitigate this bug, and some older hardware may never see an update. If you do not agree, please move along and discuss the kernel leak in the appropriate thread. We came over here strictly to discuss uMatrix/uBlock, and avoid side channel discussion in the other thread.