CVE-2025-34502

The record

Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.

Affected packages

Related vulnerabilities

• CVE-2025-34503 Deck Mate 1 executes firmware directly from an external EEPROM without verifying… CWE-1326