My question is, how can I prevent this attack?
Setting up a new system again will obviously not prevent this,
( and comes with the extra hassle that I need to renew the license of the installed Pianoteq software I want to use )
dtoverlay disable-bt in boot.config did not fix it.
Investigating more whats going on will expose the system to the attack.
Whats surprising me is that I dont find any info about this vulnerability.
(I somehow have doubts s.o. in the house knows about rare or advanced or even 0-day attacks.)
It's also not quite clear to me how it actually works.
One thing I considered was that it actually is a defective keyboard on the 400 itself, but I think we can rule this out since it would not result in systematic behaviour.
And the keyboard was not used except for booting, I had initially set login to auto (risk?), since it is a piano synthesis, which I want to start automatically without the need for a monitor and mouse.
Setting up a new system again will obviously not prevent this,
( and comes with the extra hassle that I need to renew the license of the installed Pianoteq software I want to use )
dtoverlay disable-bt in boot.config did not fix it.
Investigating more whats going on will expose the system to the attack.
Whats surprising me is that I dont find any info about this vulnerability.
(I somehow have doubts s.o. in the house knows about rare or advanced or even 0-day attacks.)
It's also not quite clear to me how it actually works.
One thing I considered was that it actually is a defective keyboard on the 400 itself, but I think we can rule this out since it would not result in systematic behaviour.
And the keyboard was not used except for booting, I had initially set login to auto (risk?), since it is a piano synthesis, which I want to start automatically without the need for a monitor and mouse.
Statistics: Posted by gemma — Mon Feb 02, 2026 4:40 am