captainkangaroo@discuss.tchncs.de to Linux@lemmy.ml · 5 months agoIntel Linux Patch Would Report Outdated CPU Microcode As A Security Vulnerabilitywww.phoronix.comexternal-linkmessage-square17fedilinkarrow-up195arrow-down11
arrow-up194arrow-down1external-linkIntel Linux Patch Would Report Outdated CPU Microcode As A Security Vulnerabilitywww.phoronix.comcaptainkangaroo@discuss.tchncs.de to Linux@lemmy.ml · 5 months agomessage-square17fedilink
minus-squareryannathans@aussie.zonelinkfedilinkarrow-up4·5 months agoHow does it know if the microcode is outdated?
minus-squarenanook@friendica.eskimo.comlinkfedilinkarrow-up12·5 months ago@ryannathans @captainkangaroo I’m going to make the wild assumption that the kernel will have a table of the current microcode versions at the time of it’s release, but I doubt that will get updated except by kernel upgrades.
minus-squareStrit@lemmy.linuxuserspace.showlinkfedilinkarrow-up3·5 months agoThere’s probably an efivar that reads the current microcode version.
minus-squareDaPorkchop_@lemmy.mllinkfedilinkarrow-up1·5 months agoDebian-based distros (and probably most othera as well) actually have a package called “intel-microcode” which gets updated fairly regularly.
How does it know if the microcode is outdated?
@ryannathans @captainkangaroo I’m going to make the wild assumption that the kernel will have a table of the current microcode versions at the time of it’s release, but I doubt that
will get updated except by kernel upgrades.
There’s probably an efivar that reads the current microcode version.
Debian-based distros (and probably most othera as well) actually have a package called “intel-microcode” which gets updated fairly regularly.