Minisforum has drawn sharp criticism for refusing to patch critical BIOS security vulnerabilities on its HM80 mini PC, even after AMD released the necessary firmware fix. This refusal leaves owners of the mid-2021 device exposed to known security risks, highlighting a troubling gap in long-term hardware support for older models. Users who rely on the HM80 for secure computing must now decide whether to accept the risk or replace their hardware entirely.
Vendor ignores AMD firmware patch for 2021 mini PC
The dispute centers on the HM80, a mini PC launched in mid-2021 powered by the AMD Ryzen 7 4800U processor. AMD had previously released an AGESA microcode update designed to address firmware vulnerabilities across older AMD socket platforms. Despite the availability of this fix, Minisforum has not packaged the AGESA update into a BIOS release for the HM80. This means the device remains unpatched against security flaws that the chip manufacturer already resolved.
User u/woyzeckpompo on Reddit accused Minisforum of ignoring the security issue and suggested the company is prioritizing new sales over lifecycle support. The user reported that support staff advised purchasing a newer model instead of providing a fix, citing warranty expiration. This stance is particularly contentious because the security defect has been present in the hardware since its initial manufacture. The company has not issued a public statement addressing these specific claims or the validity of the user's report.
The specific CVE or vulnerability details remain unnamed in the source material, making it impossible to confirm which exact AMD advisory applies. This lack of specificity does not diminish the core issue, which is the vendor's refusal to apply a known, manufacturer-provided fix. The user intends to file complaints with European consumer protection bodies, including Italy's AGCM, to challenge the lack of support. Minisforum's silence leaves the community waiting for an official response to these serious allegations.
Source: NotebookCheck




Discussion
0 comments