TUXEDO OS update closes sinkclose gap in AMD processors - TUXEDO Computers

  ATTENTION: To use our store you have to activate JavaScript and deactivate script blockers!  
Thank you for your understanding!

TUXEDO OS update closes sinkclose gap in AMD processors

Security researchers at IOActive have uncovered a critical vulnerability in AMD CPUs that has existed for nearly two decades and affects countless processors. The vulnerability, known as Sinkclose, allows attackers to execute software in System Management Mode (SMM), a particularly privileged mode that is invisible to the operating system and other applications.

System Management Mode is typically used for low-level operations such as controlling hardware components or power management and operates at the highest protection ring, ring -2. Attackers could exploit the sinkhole to install bootkits that are invisible to the operating system or antivirus software and grant them full access to the system.

Sinkclose security vulnerability in AMD processors

Such a malware infection is not only difficult to detect, but also extremely time-consuming to remove. According to IOActive, removing the malware requires the use of a special hardware-based programming tool, the SPI Flash Programmer, to scan the memory directly. In the worst case scenario, this could result in the affected computer possibly no longer being fully functional

Although exploiting the Sinkclose vulnerability (CVE-2023–31315) is not easy due to its complexity and would require local root privileges, the researchers warn that new vulnerabilities are regularly discovered that allow the necessary kernel access. Attacks that grant kernel-level access are particularly relevant for state-sponsored hackers.

AMD provides a list of affected CPUs on its website, with updates already available for some Epyc, Athlon, and Ryzen processors. However, not all impacted processors will receive an update: the Ryzen 1000, 2000, and 3000 series are excluded, as reported by the German IT blog Computerbase. AMD states that these processors will no longer be supported due to their age; the Ryzen 1000 was released in 2017.

Update 21.08.2024: According to the British magazine The Register, AMD has decided to provide patches for Ryzen 3000 CPUs after all due to public pressure. However, the decision remains in place for older CPUs from the Ryzen 1000 and 2000 series. These processors will not be patched.

Updates already integrated in TUXEDO OS

Updates are already available for Linux that mitigate the error. They must be integrated into the system by the distributors. This has already been done for TUXEDO OS and other major Linux distros such as Debian or Ubuntu. The updates are included in the amd64-microcode package, which is automatically installed with the usual updates on your computer installed with TUXEDO OS.

For a final bug fix, the system requires a BIOS/firmware update provided by AMD and the motherboard manufacturers. We will keep you informed about this via This Week in TUXEDO OS and our Newsletter.

Changelog: amd64-microcode

  • Update package data from linux-firmware 20240709–141-g59460076 (closes: #1076128)
  • SECURITY UPDATE: Mitigates „Sinkclose“ CVE-2023–31315 (AMD-SB-7014) on AMD Epyc processors: SMM lock bypass - Improper validation in a model specific register (MSR) could allow a malicious program with ring 0 access (kernel) to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution. Note: a firmware update is recommended for AMD Epyc (to protect the system as early as possible). Many other AMD processor models are also vulnerable to SinkClose, and can only be fixed by a firmware update at this time.
  • Updated Microcode patches:
    • Family=0x17 Model=0x01 Stepping=0x02: Patch=0x0800126f
    • Family=0x17 Model=0x31 Stepping=0x00: Patch=0x0830107c
    • Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a00107a
    • Family=0x19 Model=0x11 Stepping=0x02: Patch=0x0a101248
    • Family=0x19 Model=0xa0 Stepping=0x02: Patch=0x0aa00215
    • Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001238
    • Family=0x19 Model=0x11 Stepping=0x01: Patch=0x0a101148
    • Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d5
  • README.Debian: „late“ microcode updates are unsupported in Debian (closes: #1074514)
  • postinst: use dpkg-trigger to activate update-initramfs, this enables dracut integration (closes: #1000193)
  • postrm: activate the update-initramfs dpkg trigger on remove/purge instead of always executing update-initramfs directly, just like it was done for postinst in 3.20240710.1: call update-initramfs directly only if the dpkg-trigger activation call fails