Skip to content

Conflict with microcode-updates via lvfs? / issues with ucode-updates on not-affected CPU? #86

Open
@VeldoraTheDragon

Description

@VeldoraTheDragon

I am currently utilizing the microcode updates provided by Lenovo on the LVFS for my T16 Gen1.

However, recent CVE's (CVE-2023-39368, CVE-2023-38575, CVE-2023-28746) were ignored by Lenovo until 2024-05-09 with the release of CVE-2023-45733, even though the other three CVe's all had a higher CVSS scores than CVE-2023-45733.

Since I don't want to give up the option for firmware-updates via lvfs, microcode-updates are still getting installed on my device via lvfs, when I update the firmware of it.

  1. Now my question is, if I switch to the Arch intel-ucode package for the microcode updates, will they conflict with the microcode updates published by lenovo on the lvfs or will everything be fine?

  2. Will there be any problems, if I install every microcode-update, even though it doesn't affect my CPU?

I'd appreciate every answer I can get, so I can decide which way I want to go.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions