# AMD-SB-7009: Any BIOS update in preparation for the AMD FWs?

**URL:** <https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334>\
**Category:** Framework Laptop 13\
**Created:** [February 15, 2024, 6:41am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334 "2024-02-15T06:41:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ck\_two](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ck_two/32/22380_2.png) [@ck\_two](https://community.frame.work/u/ck_two)\
**Post date:** [February 15, 2024, 6:41am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/1 "2024-02-15T06:41:52Z")

</div>

It looks like the AMD FWs are affected by some of the security issues described in AMD’s recent security bulletin AMD-SB-7009 ([https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7009.html](https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7009.html)).

My question to the FW folks around here: Do you have a BIOS update in preparation to mitigate these issues?

---

<div class="post-metadata">

**Author:** ![Jorg\_Mertin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jorg_mertin/32/47951_2.png) [@Jorg\_Mertin](https://community.frame.work/u/Jorg_Mertin)\
**Post date:** [February 15, 2024, 8:54am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/2 "2024-02-15T08:54:24Z")

</div>

This is probably handled by a microcode update that will be loaded automatically by the Linux system when loaded.  
Note that the explanations show that the user/hacker must have gained access to your system already to exploit these.

---

<div class="post-metadata">

**Author:** ![ck\_two](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ck_two/32/22380_2.png) [@ck\_two](https://community.frame.work/u/ck_two)\
**Post date:** [February 15, 2024, 9:56am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/3 "2024-02-15T09:56:37Z")

</div>

I am not quite sure, if these will be corrected by the amd64-microcode package, since Heise’s news post ([https://www.heise.de/news/AMD-meldet-zahlreiche-Sicherheitsluecken-in-Prozessoren-9628343.html](https://www.heise.de/news/AMD-meldet-zahlreiche-Sicherheitsluecken-in-Prozessoren-9628343.html) … sorry, in German) implies that these issues are to be fixed by BIOS updates (and they tend to be well-informed).

---

<div class="post-metadata">

**Author:** ![Jorg\_Mertin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jorg_mertin/32/47951_2.png) [@Jorg\_Mertin](https://community.frame.work/u/Jorg_Mertin)\
**Post date:** [February 15, 2024, 9:59am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/4 "2024-02-15T09:59:16Z")

</div>

No problem for the German 😉

```auto
 Microcode- und Firmwareupdates sollten dagegen helfen

```

Well, both should. Sadly, on older hardware, only firmwareupdates will help, as manufacturers won’t bring out new BIOS’s. Luckily for FW owners, these devices are not that old 😉

---

<div class="post-metadata">

**Author:** ![ck\_two](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ck_two/32/22380_2.png) [@ck\_two](https://community.frame.work/u/ck_two)\
**Post date:** [February 15, 2024, 10:10am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/5 "2024-02-15T10:10:22Z")

</div>

Yes, you are right. However, they are not fully consistent:

```auto
Diese müssen Mainboard- und Computerhersteller jedoch
in ihre BIOS-Versionen einpflegen und an Endkunden verteilen.

```

Thank you for screening the post thoroughly.

At any rate I will scroll through the release notes of the amd64-microcode package next time apt presents an upgrade of that package in my Debian Bookworm.

---

<div class="post-metadata">

**Author:** ![Jorg\_Mertin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jorg_mertin/32/47951_2.png) [@Jorg\_Mertin](https://community.frame.work/u/Jorg_Mertin)\
**Post date:** [February 15, 2024, 10:38am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/6 "2024-02-15T10:38:45Z")

</div>

> [@ck\_two](#):
>
> Thank you for screening the post thoroughly.

I actually did, but the BIOS IMHO is not the right place to fix it. I just pointed to the firmware update too.

---

<div class="post-metadata">

**Author:** ![Marc\_Brooks](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/marc_brooks/32/12978_2.png) [@Marc\_Brooks](https://community.frame.work/u/Marc_Brooks)\
**Post date:** [February 17, 2024, 3:28am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/7 "2024-02-17T03:28:25Z")

</div>

Does this thread answer your questions [AMD processor vulnerabilities - Community Support - Framework Community](http://community.frame.work/t/amd-processor-vulnerabilities/45423)

---

<div class="post-metadata">

**Author:** ![ck\_two](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ck_two/32/22380_2.png) [@ck\_two](https://community.frame.work/u/ck_two)\
**Post date:** [February 17, 2024, 9:42am UTC](https://community.frame.work/t/amd-sb-7009-any-bios-update-in-preparation-for-the-amd-fws/45334/8 "2024-02-17T09:42:01Z")

</div>

Thank you so much for bringing this to my attention … and a big “thank you” to the Framework folks for being so responsive and transparent at the same time. This attitude makes the difference.
