Conversation

Notices

Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 09:17:19 JST Rich Felker
- Harry Sintonen
- The Doctor
@drwho @harrysintonen I could see doing an update *once* at setup time if the board isn't working, but not doing it again when it is working just because there's an "update available".

In conversation about 2 months ago from hachyderm.io permalink
- Embed this notice
  Harry Sintonen (harrysintonen@infosec.exchange)'s status on Friday, 19-Jun-2026 10:14:02 JST Harry Sintonen
  in reply to
  
  @dalias If you don't update you will be vulnerable to various exploits. https://en.wikipedia.org/wiki/AGESA and look for "Security fixes"
  In conversation about 2 months ago permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: auth.wikimedia.org
    
    AGESA
    
    AMD Generic Encapsulated Software Architecture (AGESA) is a procedure library developed by Advanced Micro Devices (AMD), used to perform the Platform Initialization (PI) on mainboards using their AMD64 architecture. As part of the BIOS of such mainboards, AGESA is responsible for the initialization of the CPU cores, chipset, main memory, and the HyperTransport controller. History AGESA was open sourced in early 2011, aiming to aid in the development of coreboot, a project attempting to replace PC's proprietary BIOS. However, such releases never became the basis for the development of coreboot beyond AMD's Bulldozer microarchitecture, and were subsequently halted. AGESA became particularly relevant with the AM4 platform, which AMD designed for futureproofing and served as the socket for four different generations of CPUs based on its Zen architecture. For each of these generations, a new branch of AGESA code has been released. AGESA versioning often runs separately for each of these three releases, so numbering regressions are bound to happen when going from one generation to the next. The...
- Embed this notice
  Rich Felker (dalias@hachyderm.io)'s status on Friday, 19-Jun-2026 10:14:02 JST Rich Felker
  in reply to
  - Harry Sintonen
  @harrysintonen The "security" boundary "fixed" by these fixes is the one that denies the owner of the computer access to their own computer. These are anti-fixes. For example:
  "CVE-2024-36355, Improper input validation in the System Management Mode (SMM) handler could allow an attacker with Ring0 access to write to SMRAM"
  
  In conversation about 2 months ago permalink

Public

Conversation

Notices

Feeds