intel / intel/Intel-Linux-Processor-Microcode-Data-Files

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

Ouverte
#86 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Aucune donnée de langage
Étoiles
818
Forks
86
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.