I don&#x27;t think this is meant to be a <i>security</i> fix, it&#x27;s just meant to make it so you can&#x27;t accidentally break your hardware with what seems like an unrelated filesystem command.<p>I agree that the stupid firmware is ultimately to blame, and mounting this stuff read-write is a fairly reasonable initial decision. But given the existence of this stupid firmware, the resistance to implementing an easy mitigation by mounting it read-only is insane. I can&#x27;t understand why there are any responses besides &quot;oh shit, we&#x27;d better change this.&quot;