Title: Conflict with microcode-updates via lvfs? / issues with ucode-updates on not-affected CPU? · Issue #86 · intel/Intel-Linux-Processor-Microcode-Data-Files · GitHub
Open Graph Title: Conflict with microcode-updates via lvfs? / issues with ucode-updates on not-affected CPU? · Issue #86 · intel/Intel-Linux-Processor-Microcode-Data-Files
X Title: Conflict with microcode-updates via lvfs? / issues with ucode-updates on not-affected CPU? · Issue #86 · intel/Intel-Linux-Processor-Microcode-Data-Files
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-45...
Open Graph 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 20...
X 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 unti...
Opengraph URL: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/86
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Conflict with microcode-updates via lvfs? / issues with ucode-updates on not-affected CPU?","articleBody":"I am currently utilizing the microcode updates provided by Lenovo on the LVFS for my T16 Gen1.\r\n\r\nHowever, 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.\r\n\r\nSince 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.\r\n\r\n1) 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?\r\n\r\n2) Will there be any problems, if I install every microcode-update, even though it doesn't affect my CPU?\r\n\r\nI'd appreciate every answer I can get, so I can decide which way I want to go.","author":{"url":"https://github.com/VeldoraTheDragon","@type":"Person","name":"VeldoraTheDragon"},"datePublished":"2024-10-17T07:41:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/86/Intel-Linux-Processor-Microcode-Data-Files/issues/86"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:85689fbc-e71f-0783-915e-e442eab50e81 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BB14:19A3FE:156ECE:1B81C7:698FF02B |
| html-safe-nonce | a8fca28761a0d4c41e485c66500b58a7db69033db7aa1a855d095a8e258fed85 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQjE0OjE5QTNGRToxNTZFQ0U6MUI4MUM3OjY5OEZGMDJCIiwidmlzaXRvcl9pZCI6IjYwOTc5NzQ5MzYzMzYzMzA3OTUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 4ae828119d1301c75059e2b8d291f7ceda01e6d62755dac3832e47582afac6ea |
| hovercard-subject-tag | issue:2593902954 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/intel/Intel-Linux-Processor-Microcode-Data-Files/86/issue_layout |
| twitter:image | https://opengraph.githubassets.com/7f1aa02d32dd9a2391660538677f3c8ab2eb3aa3a890d4a3c0c0b40cb1d8a38f/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/86 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/7f1aa02d32dd9a2391660538677f3c8ab2eb3aa3a890d4a3c0c0b40cb1d8a38f/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/86 |
| og:image:alt | 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 20... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | VeldoraTheDragon |
| hostname | github.com |
| expected-hostname | github.com |
| None | 42c603b9d642c4a9065a51770f75e5e27132fef0e858607f5c9cb7e422831a7b |
| turbo-cache-control | no-preview |
| go-import | github.com/intel/Intel-Linux-Processor-Microcode-Data-Files git https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git |
| octolytics-dimension-user_id | 17888862 |
| octolytics-dimension-user_login | intel |
| octolytics-dimension-repository_id | 174040030 |
| octolytics-dimension-repository_nwo | intel/Intel-Linux-Processor-Microcode-Data-Files |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 174040030 |
| octolytics-dimension-repository_network_root_nwo | intel/Intel-Linux-Processor-Microcode-Data-Files |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 3b33c5aedc9808f45bc5fcf0b1e4404cf749dac7 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width