Sorry if duplicate or already uploaded
cpuB06F5_plat07_ver00000028_2022-10-31_PRD_F5D235BB.zip (213.2 KB)
cpuB06F2_plat07_ver00000028_2022-10-31_PRD_F5D235BE.zip (213.2 KB)
cpu90675_plat07_ver00000028_2022-10-31_PRD_F5D4363B.zip (213.2 KB)
cpu90672_plat07_ver00000028_2022-10-31_PRD_F5D4363E.zip (213.2 KB)
Update on the Microcode 0xf4. ref: Affected Processors: Transient Execution Attacks & Related Security...
All the CPUs that got the 0xf4 are vulnerable to:
1- “Post-barrier Return Stack Buffer Predictions CVE-2022-26373 INTEL-SA-00706”
4- “Return Stack Buffer Underflow (RSBU) Restricted RSB Alternate Behavior (RRSBA) CVE-2022-28693 INTEL-SA-00707”
8- “Branch History Injection (BHI) CVE-2022-0001 INTEL-SA-00598”
9- “Intra-Mode BTI CVE-2022-0002 INTEL-SA-00598”
Mentioned in the 1st, 4th, 8th and 9th columns!
This could imply that the 0xf4 is a fix for these vulnerabilities! Cause the CPUs that didn’t get it are not vulnerable.
On the other hand, The CPUs with 0xf0 are vulnerable to “Return Stack Buffer Underflow (RSBU) RSB Alternate Behavior (RSBA) CVE-2022-29901 INTEL-SA-00702” menthioned in the 3rd column!
These are always exceptions 
“406E3 and 906EC”
806EC: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
906ED: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
A0652: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
A0653: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
A0655: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
A0661: 0xf4 SO NA NA SO MCU+SO MCU+SO SO SO SO NA NA
506E3: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
806E9: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
806EA: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
806EB: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
906E9: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
906EA: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
906EB: 0xf0 NA NA SO NA MCU+SO MCU+SO SO NA NA NA NA
406E3: 0xf0 NA NA SO NA MCU+SO MCU+SO NA NA NA NA NA
906EC: 0xf0 SO NA SO NA MCU+SO MCU+SO SO NA NA NA NA
I could be wrong, I don’t know. But it seems like it.
Intel cpuB0671_plat32_ver00000112_2022-12-19_PRD_0DE1BBA2
Intel cpuB06F5_plat07_ver0000002B_2022-12-18_PRD_53EBA923
Intel cpuB06F2_plat07_ver0000002B_2022-12-18_PRD_53EBA926
Intel cpu90675_plat07_ver0000002B_2022-12-18_PRD_53EDA9A3
Intel cpu90672_plat07_ver0000002B_2022-12-18_PRD_53EDA9A6
uCodes.rar (418.3 KB)
cpu806F4_plat10_ver2C000120_2022-11-07_PRD_6C023E81
cpu806F5_plat10_ver2C000120_2022-11-07_PRD_6C023E80
cpu806F6_plat10_ver2C000120_2022-11-07_PRD_6C023E7F
cpu806F8_plat10_ver2C000120_2022-11-07_PRD_6C023E7D
intel_spr.rar (583.3 KB)
Intel cpuB06A3_platC0_ver00004305_2022-09-08_PRD_46F11B93
Intel cpuB06A2_platC0_ver00004305_2022-09-08_PRD_46F11B94
Intel cpu906A4_platC3_ver00000002_2022-05-09_PRD_B48C0BF5
uCodes.rar (309.6 KB)
cpu00A10F11_ver0A101111_2022-10-27_6D89BAF6
cpu00AA0F00_ver0AA00009_2022-10-06_D518BB26
cpu00AA0F01_ver0AA00105_2022-10-31_5D60B0B4
amd.rar (16.0 KB)
cpu00A00F10_ver0A001078_2023-01-17_F49EB7FC
cpu00A00F11_ver0A0011CE_2023-01-14_28D4B525
cpu00A00F12_ver0A001231_2023-01-17_52F4A3B3
AMD.zip (17.0 KB)
cpu606C1_plat10_ver01000211_2022-09-23_PRD_BFBF4122
cpu806A1_plat10_ver00000032_2022-09-07_PRD_C139C424
cpu806F4_plat10_ver2C000170_2022-12-19_PRD_8DFF74FA
cpu806F5_plat10_ver2C000170_2022-12-19_PRD_8DFF74F9
cpu806F6_plat10_ver2C000170_2022-12-19_PRD_8DFF74F8
cpu806F8_plat10_ver2C000170_2022-12-19_PRD_8DFF74F6
cpu906A3_plat80_ver00000429_2023-01-11_PRD_9FF72132
cpu906A4_plat80_ver00000429_2023-01-11_PRD_9FF72131
cpu906C0_plat01_ver24000024_2022-09-02_PRD_B8A9E091
230214.rar (1.1 MB)
Intel cpuB06E0_plat01_ver0000000F_2022-09-21_PRD_C0DCA789
cpuB06E0_plat01_ver0000000F_2022-09-21_PRD_C0DCA789.rar (131.3 KB)
cpu90672_plat07_ver0000002C_2023-01-04_PRD_CEE1C7DD.bin
cpu90675_plat07_ver0000002C_2023-01-04_PRD_CEE1C7DA.bin
cpuB06F2_plat07_ver0000002C_2023-01-04_PRD_CEDFC75D.bin
cpuB06F5_plat07_ver0000002C_2023-01-04_PRD_CEDFC75A.bin
cpuB0670_plat02_ver0000000E_2022-02-20_PRD_0A83935A.bin
cpuB0671_plat32_ver00000112_2022-12-19_PRD_0DE1BBA2.bin
Intel.rar (1.2 MB)
cpu50656_platBF_ver04003303_2022-08-26_PRD_A9292882
cpu50657_platBF_ver05003303_2022-08-26_PRD_F9CBA561
Intel.rar (74.4 KB)
Intel cpuB0671_plat32_ver00000113_2023-02-06_PRD_7FC06AF8
B0671 plat32 ver113
Showed as new with MCExtractor-1.80.0-r260
cpuB0671_plat32_ver00000113_2023-02-06_PRD_7FC06AF8.zip (203.2 KB)
I cant find a new MCE.exe but the new DB rev 260 requieres a new version 1.80
Upon today release of the KB5019178 and having mcupdate_GenuineIntel.dll as 22621.1341 (bios mcode not related here because its not updated or mod), just noticed that system (22621.1391) is still using (cpuidA0653) the F0 mcode and not the F4 as reported to be used in this KB for using the F4 from 2022/07/31… whats the deal here in this package… feedback is appreciated.
From your link:
Intel Platform Update (IPU) 2022.1 that is dated June 2022 contains fixes for security vulnerabilities including Memory-Mapped I/O (MMIO) Side-Channel Attack.
Look for A0653 => shows F4 but 2022.3 (and F4 is dated 07/31/2022)
Speculation control settings for CVE-2017-5715 [branch target injection]
Hardware support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: True
Speculation control settings for CVE-2017-5754 [rogue data cache load]
Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID performance optimization is enabled: True [not required for security]
Speculation control settings for CVE-2018-3639 [speculative store bypass]
Hardware is vulnerable to speculative store bypass: True
Hardware support for speculative store bypass disable is present: True
Windows OS support for speculative store bypass disable is present: True
Windows OS support for speculative store bypass disable is enabled system-wide: True
Speculation control settings for CVE-2018-3620 [L1 terminal fault]
Hardware is vulnerable to L1 terminal fault: False
Speculation control settings for MDS [microarchitectural data sampling]
Windows OS support for MDS mitigation is present: True
Hardware is vulnerable to MDS: False
Speculation control settings for SBDR [shared buffers data read]
Windows OS support for SBDR mitigation is present: True
Hardware is vulnerable to SBDR: True
Windows OS support for SBDR mitigation is enabled: True
Speculation control settings for FBSDP [fill buffer stale data propagator]
Windows OS support for FBSDP mitigation is present: True
Hardware is vulnerable to FBSDP: True
Windows OS support for FBSDP mitigation is enabled: True
Speculation control settings for PSDP [primary stale data propagator]
Windows OS support for PSDP mitigation is present: True
Hardware is vulnerable to PSDP: True
Windows OS support for PSDP mitigation is enabled: True
BTIHardwarePresent : True
BTIWindowsSupportPresent : True
BTIWindowsSupportEnabled : True
BTIDisabledBySystemPolicy : False
BTIDisabledByNoHardwareSupport : False
BTIKernelRetpolineEnabled : False
BTIKernelImportOptimizationEnabled : True
KVAShadowRequired : True
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : True
KVAShadowPcidEnabled : True
SSBDWindowsSupportPresent : True
SSBDHardwareVulnerable : True
SSBDHardwarePresent : True
SSBDWindowsSupportEnabledSystemWide : True
L1TFHardwareVulnerable : False
L1TFWindowsSupportPresent : True
L1TFWindowsSupportEnabled : False
L1TFInvalidPteBit : 0
L1DFlushSupported : True
MDSWindowsSupportPresent : True
MDSHardwareVulnerable : False
MDSWindowsSupportEnabled : True
FBClearWindowsSupportPresent : True
SBDRSSDPHardwareVulnerable : True
FBSDPHardwareVulnerable : True
PSDPHardwareVulnerable : True
FBClearWindowsSupportEnabled : True
Yes my friend powershell and all the stuff that we know around, reports F0…
The idea that the KB give us is that the F4 would be added to the sys by this update…seems not, thats what im trying to figure out.
Indeed we know this F4 already from individual mcodes, just thought that now MS was adding it to mcupdate…
To my recollection, Microsoft never released a microcode update package that included the latest of anything. I guess they have their own verification procedure. This is partly contradicted by the fact that in the past, the Insider Preview (Dev channel) versions were the ones that had the latest microcode versions. The current Windows 11 update is dated 23 February 2023 , and the latest microcode included is dated February 2022.
If you are interested, you can see what has changed (Windows 11, and Windows 10).. The green - red pairs are the interesting ones.
This is the second update for Windows 10 (one every 24 months from release), and the first for Windows 11 (9 months after release).
It is clear that you need to keep the BIOS fresh, not rely on Microsoft.
Sure…but dont want the trouble, you see this a Z490 from MSI without USB BFB and i got lucky so far in all bios updates without any issues that others still report today, windows is using the same mcode as the bios, the F0… so let it be as it is, not gonna play with her bios and update the mcode.
Never checked the old mcupdate file, but now this one (22621.1341) is on F0, if so they just updated from E0 to F0 and the F4 maybe in by 2024/25…lol
And thank you for all the info you gathered.