6502 can do it in one. 12 opcodes are glitched in a way that permanently halts the CPU, by causing it to never reset the internal tick counter (...sortof) that starts the next instruction. Recovery is only possible with a power cycle.

6502 doesn’t host Linux :)

Being able to crash a Linux kernel from unprivileged user code is more fun.