CPU Microcode - Revision history

Ckujau: with grep it shows the name of the vulnerability too

2026-02-11T21:02:51Z

with grep it shows the name of the vulnerability too

← Older revision		Revision as of 21:02, 11 February 2026
Line 39:		Line 39:
	== Check if CPU mitigation is working ==		== Check if CPU mitigation is working ==
	This command not only shows if microcode is working, but other CPU vulnerabilities affected:		This command not only shows if microcode is working, but other CPU vulnerabilities affected:
	{{cmd\|~~cat~~ /sys/devices/system/cpu/vulnerabilities/*}}		{{cmd\|grep -r . /sys/devices/system/cpu/vulnerabilities/}}

	[[Category:Security]]		[[Category:Security]]

2024-12-30T01:14:20Z

← Older revision		Revision as of 01:14, 30 December 2024
Line 36:		Line 36:

	{{Todo\|Example needed for VIA CPUs, they seem to print slightly differently.}}		{{Todo\|Example needed for VIA CPUs, they seem to print slightly differently.}}

			== Check if CPU mitigation is working ==
			This command not only shows if microcode is working, but other CPU vulnerabilities affected:
			{{cmd\|cat /sys/devices/system/cpu/vulnerabilities/*}}

	[[Category:Security]]		[[Category:Security]]

2024-12-29T12:34:54Z

← Older revision		Revision as of 12:34, 29 December 2024
Line 25:		Line 25:

	Example for Intel:		Example for Intel:
	~~{{codeline\|~~[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}		<pre>
			[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4
			</pre>

	{{Todo\|Example needed for ~~AMD and~~ VIA CPUs, they seem to print slightly differently.}}		Example for AMD:
			<pre>
			[ 11.442146] microcode: Current revision: 0x0a0011d5
			[ 11.447027] microcode: Updated early from: 0x0a0011d3
			</pre>

			{{Todo\|Example needed for VIA CPUs, they seem to print slightly differently.}}
	[[Category:Security]]		[[Category:Security]]

2023-08-31T16:50:50Z

Verifying that the microcode image has loaded: todo

← Older revision		Revision as of 16:50, 31 August 2023
Line 24:		Line 24:
	If the microcode initrd image was loaded, the microcode update driver will print a signature and revision		If the microcode initrd image was loaded, the microcode update driver will print a signature and revision

			Example for Intel:
	{{codeline\|[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}		{{codeline\|[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}

			{{Todo\|Example needed for AMD and VIA CPUs, they seem to print slightly differently.}}
	[[Category:Security]]		[[Category:Security]]

2023-08-07T00:51:31Z

Added security category

← Older revision		Revision as of 00:51, 7 August 2023
Line 25:		Line 25:

	{{codeline\|[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}		{{codeline\|[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}
			[[Category:Security]]

2023-08-06T18:12:35Z

Mention limine and use the path template.

← Older revision		Revision as of 18:12, 6 August 2023
Line 17:		Line 17:
	{{cmd\|apk add {{pkg\|intel-ucode}}}}		{{cmd\|apk add {{pkg\|intel-ucode}}}}

	If you are using syslinux or grub in a typical setup, the packages will automatically append your extlinux.conf or grub.conf file and merely a reboot will be required to run the new microcode. Users using UEFI's built-in boot manager will have to use efibootmgr to add a second initrd line.		If you are using syslinux or grub in a typical setup, the packages will automatically append your {{path\|extlinux.conf}} or {{path\|grub.conf}} file and merely a reboot will be required to run the new microcode. Users using UEFI's built-in boot manager will have to use efibootmgr to add a second initrd line. Likewise if you are using the limine bootoader will need to add a 2nd MODULE_PATH directive in {{path\|limine.cfg}} pointing to the ucode file.

	== Verifying that the microcode image has loaded ==		== Verifying that the microcode image has loaded ==

2023-08-06T17:53:30Z

Obtaining microcode updates on Alpine: Added warning for Broadwell and Haswell too.

← Older revision		Revision as of 17:53, 6 August 2023
Line 7:		Line 7:
	== Obtaining microcode updates on Alpine ==		== Obtaining microcode updates on Alpine ==

	{{Warning\| Intel Atom ~~users~~ with ~~a "~~PSE ~~erratum" message in dmesg: The microcode update~~ can only be ~~applied by~~ BIOS or UEFI update, not ~~via initrd!~~}}		{{Warning\| Certain Intel CPUs, such Intel Atom with PSE errata, and Intel Haswell + Broadwell with TSX errata, can only be fixed via BIOS or UEFI update (which includes microcode); if you are using one of these CPUs, please do not use the instructions below}}

	On Alpine Linux, CPU microcode is loaded early via initrd images, premade images are available from packages:		On Alpine Linux, CPU microcode is loaded early via initrd images, premade images are available from packages:

2023-08-06T17:49:08Z

Obtaining microcode updates on Alpine: Added warning for Intel Atom PSE errata: This can only be fixed via firmware update

← Older revision		Revision as of 17:49, 6 August 2023
Line 6:		Line 6:

	== Obtaining microcode updates on Alpine ==		== Obtaining microcode updates on Alpine ==

			{{Warning\| Intel Atom users with a "PSE erratum" message in dmesg: The microcode update can only be applied by BIOS or UEFI update, not via initrd!}}

	On Alpine Linux, CPU microcode is loaded early via initrd images, premade images are available from packages:		On Alpine Linux, CPU microcode is loaded early via initrd images, premade images are available from packages:

2023-08-06T16:35:46Z

Verifying that the microcode image has loaded: Use HTML entities so the codeline template will behave

← Older revision		Revision as of 16:35, 6 August 2023
Line 21:		Line 21:
	{{cmd\|dmesg \| grep microcode}}		{{cmd\|dmesg \| grep microcode}}
	If the microcode initrd image was loaded, the microcode update driver will print a signature and revision		If the microcode initrd image was loaded, the microcode update driver will print a signature and revision
	{{codeline\|[ 2.198775] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}
			{{codeline\|[ 2.198775 ] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}

2023-08-06T16:30:34Z

Verifying: don´t look for the driver version, it is ALWAYS printed, look for the revision, it is only printed if microcode was fed to the kernel

← Older revision		Revision as of 16:30, 6 August 2023
Line 20:		Line 20:
	Run the command:		Run the command:
	{{cmd\|dmesg \| grep microcode}}		{{cmd\|dmesg \| grep microcode}}
	If the microcode initrd image was loaded, the microcode update driver ~~version~~ will ~~appear in the dmesg output~~		If the microcode initrd image was loaded, the microcode update driver will print a signature and revision
	{{codeline\|[ 0.~~624507~~] microcode: ~~Microcode Update Driver: v2.2.~~}}		{{codeline\|[ 2.198775] microcode: sig=0x6fd, pf=0x80, revision=0xa4}}