Actually, node <21.2.0 uses a base64 library that crashes the process with an illegal instruction (caused by a flawed AVX support detection routine) if you're 1. running it on certain Skylake CPUs, and 2. have enabled kernel mitigations for the "gather data sampling" vulnerability.
The fix has not yet been backported to node's 18.x branch.
And Electron <27 contains an *additional* similar bug in node's simdutf because they don't use the latest node 18.x release.
Actually, node <21.2.0 uses a base64 library that crashes the process with an illegal instruction (caused by a flawed AVX support detection routine) if you're 1. running it on certain Skylake CPUs, and 2. have enabled kernel mitigations for the "gather data sampling" vulnerability.
Gregory's Server
@qlp @thomasfuchs @jasonsando
Actually, node <21.2.0 uses a base64 library that crashes the process with an illegal instruction (caused by a flawed AVX support detection routine) if you're
1. running it on certain Skylake CPUs, and
2. have enabled kernel mitigations for the "gather data sampling" vulnerability.
The fix has not yet been backported to node's 18.x branch.
And Electron <27 contains an *additional* similar bug in node's simdutf because they don't use the latest node 18.x release.
@qlp @thomasfuchs @jasonsando
Actually, node <21.2.0 uses a base64 library that crashes the process with an illegal instruction (caused by a flawed AVX support detection routine) if you're
1. running it on certain Skylake CPUs, and
2. have enabled kernel mitigations for the "gather data sampling" vulnerability.