Blame SOURCES/README.caveats

c59b13
The microcode_ctl package contains microcode files (vendor-provided binary data
c59b13
and/or code in proprietary format that affects behaviour of a device) for Intel
c59b13
CPUs that may be loaded into the CPU during boot.
c59b13
c59b13
The microcode_ctl package contains provisions for some issues related
c59b13
to microcode loading.  While those provisions are expected to suit most users,
c59b13
several knobs are available in order to provide ability to override the default
c59b13
behaviour.
c59b13
c59b13
c59b13
General behaviour
c59b13
=================
c59b13
In RHEL 8 (as well as RHEL 7 before it), there are currently two main handlers
c59b13
for CPU microcode update:
c59b13
 * Early microcode update. It uses GenuineIntel.bin or AuthenticAMD.bin file
c59b13
   placed at the beginning of an initramfs image
c59b13
   (/boot/initramfs-KERNEL_VERSION.img, where "KERNEL_VERSION" is a kernel
c59b13
   version in the same format as provided by "uname -r") as a source
c59b13
   of microcode data, and is performed very early during the boot process
c59b13
   (if the relevant microcode file is available in the aforementioned file).
c59b13
 * On-demand (late) microcode update. It can be triggered by writing "1" to
c59b13
   /sys/devices/system/cpu/microcode/reload file (provided my the "microcode"
c59b13
   module). It relies on request_firmware infrastructure, which searches (and
c59b13
   loads, if found) microcode from a file present in one of the following
c59b13
   directories (in the search order):
c59b13
       /lib/firmware/updates/KERNEL_VERSION/
c59b13
       /lib/firmware/updates/
c59b13
       /lib/firmware/KERNEL_VERSION/
c59b13
       /lib/firmware/
c59b13
  (there is also an additional directory that can be configured via the
c59b13
  "fw_path_para" module option of the "firmware_class" module; as this module
c59b13
  is built-in in RHEL kernel, a boot parameter "firmware_class.fw_path_para"
c59b13
  should be used for that purpose; this is out of the document's scope, however)
c59b13
c59b13
The firmware for Intel CPUs is searched in "intel-ucode" subdirectory, and for
c59b13
AMD CPUs, a file under "amd-ucode" is searched.
c59b13
c59b13
For Intel CPUs, the name of the specific microcode file the kernel tries to load
c59b13
has the format "FF-MM-SS", where "FF" is the family number, "MM" is the model
c59b13
number, and "SS" is the stepping. All those numbers are zero-filled to two digits
c59b13
and are written in hexadecimal (letters are in the lower case).  For AMD CPUs,
c59b13
the file name has the format "microcode_amd_famFFh.bin", where "FF" is the
c59b13
family number, written in hexadecimal, letters are in the lower case, not
c59b13
zero-filled.
c59b13
c59b13
The early microcode is placed into initramfs image by the "dracut" script, which
c59b13
scans the aforementioned subdirectories of the configured list of firmware
c59b13
directories (by default, the list consists of two directories in RHEL 8,
c59b13
"/lib/firmware/updates" and "/lib/firmware").
c59b13
c59b13
In RHEL 8, AMD CPU microcode is shipped as a part of the linux-firmware package,
c59b13
and Intel microcode is shipped as a part of the microcode_ctl package.
c59b13
c59b13
The microcode_ctl package currently includes the following:
c59b13
 * Intel CPU microcode files, placed in /usr/share/microcode_ctl/intel-ucode
c59b13
   directory (currently there are none);
c59b13
 * A dracut module, /usr/lib/dracut/modules.d/99microcode_ctl-fw_dir_override,
c59b13
   that controls which additional firmware directories will be added to dracut's
c59b13
   default configuration;
c59b13
 * A dracut configuration file, /usr/lib/dracut/dracut.conf.d/01-microcode.conf,
c59b13
   that enables inclusion of early microcode to the generated initramfs
c59b13
   in dracut;
c59b13
 * A dracut configuration file,
c59b13
   /usr/lib/dracut/dracut.conf.d/99-microcode-override.conf, that provides a way
c59b13
   to quickly disable 99microcode_ctl-fw_dir-override dracut module;
c59b13
 * A systemd service file, microcode.service, that triggers microcode reload
c59b13
   late during boot;
c59b13
 * A set of directories in /usr/share/microcode_ctl/ucode_with_caveats, each
c59b13
   of which contains configuration and related data for various caveats related
c59b13
   to microcode:
c59b13
   * readme - description of caveat and related information,
c59b13
   * config - caveat configuration file, with syntax as described in "Caveat
c59b13
     configuration" section below,
c59b13
   * intel-ucode - directory containing microcode files related to the caveat;
c59b13
 * A set of support scripts, placed in /usr/libexec/microcode_ctl:
c59b13
   * "check_caveats" is an utility script that performs checks of the target
c59b13
     kernel (and running CPU) in accordance with caveat configuration files
c59b13
     in ucode_with_caveats directory and reports whether it passes them or not,
c59b13
   * "reload_microcode" is a script that is called by microcode.service and
c59b13
     triggers microcode reloading (by writing "1" to
c59b13
     /sys/devices/system/cpu/microcode/reload) if the running kernel passes
c59b13
     check_caveats checks,
c59b13
   * "update_ucode" is a script that populates symlinks to microcode files
c59b13
     in /lib/firmware, so it can be picked up by relevant kernels for the late
c59b13
     microcode loading.
c59b13
c59b13
Also, microcode_ctl RPM includes triggers that run update_ucode script on every
c59b13
installation or removal of a kernel RPM in order to provide microcode files
c59b13
for newly installed kernels and cleanup symlinks for the uninstalled ones.
c59b13
c59b13
5532bf
Microcode file structure
5532bf
------------------------
5532bf
Intel x86 CPU microcode file (that is, one that can be directly consumed
5532bf
by the CPU/kernel, and not its text representation such as used in microcode.dat
5532bf
files) is a bundle of concatenated microcode blobs.  Each blob has a header,
5532bf
payload, and an optional additional data, as follows (for additional information
5532bf
please refer to "Intel® 64 and IA-32 Architectures Software Developer’s Manual"
5532bf
[1], Volume 3A, Section 9.11.1 "Microcode Update"):
5532bf
 * Header (48 bytes)
5532bf
    * Header version (unsigned 32-bit integer): version number of the update
5532bf
      header.  Must be 0x1.
5532bf
    * Microcode revision (signed 32-bit integer)
5532bf
    * Microcode date (unsigned 32-bit integer): encoded as BCD in mmddyyyy format
5532bf
      (0x03141592 is 1592-03-14 in ISO 8601)
5532bf
    * CPU signature (unsigned 32-bit integer): CPU ID, as provided
5532bf
      by the CPUID (EAX = 0x1) instruction in the EAX register:
5532bf
       * bits 31..28: reserved
5532bf
       * bits 27..20: "Extended Family", summed with the Family field value
5532bf
       * bits 19..16: "Extended Model", bits 7..4 of the CPU model
5532bf
       * bits 15..14: reserved
5532bf
       * bits 13..12: "Processor Type", non-zero value (other than the "primary
5532bf
         processor") so far used only for the Deschutes (Pentium II) CPU family,
5532bf
         with the processor type of 1, to signify it is an Overdrive processor:
5532bf
         CPUID 0x1632.
5532bf
       * bits 11..08: Family, summed with the Extended Family field value
5532bf
       * bits 07..04: Model (bits 3..0)
5532bf
       * bits 03..00: Stepping
5532bf
      In short, microcode file with Family-Model-Stepping of uv-wx-0z corresponds
5532bf
      to CPUID 0x0TUw0Vxz, where uv = TU + V, with V usually being 0xF when
5532bf
      uv >= 16; with Family being 6 on most of recent Intel CPUs this transforms
5532bf
      into 0x000w06xz.  Please also refer to README.intel-ucode, section "About
5532bf
      Processor Signature, Family, Model, Stepping and Platform ID"
5532bf
      for additional information.
5532bf
    * Checksum (unsigned 32-bit integer): correct if sum (in base 1 << 32) of all
5532bf
      the 32-bit integers comprising the microcode amounts to 0.
5532bf
    * Loader version (unsigned 32-bit integer): 0x1.
5532bf
    * Platform ID mask (unsigned 32-bit integer): lower 8 bits indicate the set
5532bf
      of possible values of bits 52..50 of MSR 0x17 ("Platform ID").  In old
5532bf
      (up to Pentium II) microcode blobs the mask may be zero.
5532bf
    * Data size (unsigned 32-bit integer): size of the Payload in bytes,
5532bf
      has to be divisible by 4.  0 means 2000.
5532bf
    * Total size (unsigned 32-bit integer): total microcode blob size (including
5532bf
      header and extended header), has to be divisible by 1024.  0 means 2048.
5532bf
    * Reserved (12 bytes).
5532bf
 * Payload
5532bf
 * Additional data (optional, 20 + 12 * n bytes)
5532bf
    * Extended signature table header (20 bytes)
5532bf
       * Extended signature count (unsigned 32-bit integer)
5532bf
       * Checksum (unsigned 32-bit integer): correct if sum (in base 1 << 32)
5532bf
         of all the 32-bit integers comprising the extender signature table
5532bf
         amounts to 0.
5532bf
       * Reserved (12 bytes).
5532bf
    * Extended signature (12 bytes each)
5532bf
       * CPU signature (unsigned 32-bit integer): see the description of the CPU
5532bf
         signature field in the Header above.
5532bf
       * Platform ID mask (unsigned 32-bit integer): see the description
5532bf
         of the Platform ID mask field in the Header above.
5532bf
       * Checksum (unsigned 32-bit integer): correct if sum (in base 1<< 32)
5532bf
         of all the 32-bit integers comprising the Header (with CPU signature
5532bf
         and Platform ID mask fields replaced with the values from this signature)
5532bf
         and the Payload amounts to 0.  Note that since External signature table
5532bf
         header has its own checksum, sum of all its 32-bit values amounts to 0,
5532bf
         so the Checksum in the Header and in the Extended signature will be
5532bf
         the same if the values of CPU signature and Platform ID mask fields
5532bf
         are the same,
5532bf
5532bf
[1] https://software.intel.com/content/www/us/en/develop/download/intel-64-and-ia-32-architectures-sdm-combined-volumes-1-2a-2b-2c-2d-3a-3b-3c-3d-and-4.html
5532bf
5532bf
c59b13
Caveat configuration
c59b13
--------------------
c59b13
There is a directory for each caveat under
c59b13
/usr/share/microcode_ctl/ucode_with_caveats, containing the following files:
c59b13
 * "config", a configuration file for the caveat;
c59b13
 * "readme", that contains description of the caveat;
c59b13
 * set of related associated microcode files.
c59b13
c59b13
"config" file is a set of lines each containing option name and its value,
c59b13
separated by white space.  Currently, the following options are supported:
c59b13
 * "model" option, which has format "VENDOR_ID FF-MM-SS", that specifies
c59b13
   to which CPU model the caveat is applicable (check_caveats ignores caveats
c59b13
   with non-matching models if "-m" option is passed to it). Can be set
c59b13
   in the configuration file only once (the last provided value is used).
c59b13
 * "vendor" option specifies CPUs of which vendor (as provided
c59b13
   in the /proc/cpuinfo file) the caveat is applicable to (check_caveats
c59b13
   ignores caveats with non-matching models when it is invoked with "-m"
c59b13
   option). Can be set in the configuration file only once.
c59b13
 * "path" is a glob pattern that specifies set of microcode files associated
c59b13
   with the caveat as a relative path to the caveat directory. This option
c59b13
   is used for populating files in /lib/firmware by update_ucode script and
c59b13
   for matching microcode file when dracut is run in host-only mode
c59b13
   (as in that case it uses only the first directory in firmware directory list
c59b13
   to look for the microcode file applicable to the host CPU).  Can be set
c59b13
   in the configuration file multiple times.
c59b13
 * "kernel" is a minimal kernel version that supports proper handling
c59b13
   of the related microcode files during late microcode load.  It may be
c59b13
   provided in one of the following formats that affect the way it is compared
c59b13
   to the running kernel version:
c59b13
    * A.B.C (where A, B, and C are decimal numbers), "upstream version". In this
c59b13
      case, simple version comparison against the respective part of the running
c59b13
      kernel version is used, and the running kernel version should be greater
c59b13
      or equal than the version provided in the configuration option in order
c59b13
      for comparison to succeed (that is, the first part, major version number,
c59b13
      of the running kernel version should be greater than the value provided
c59b13
      in the configuration option, or those should be equal and the second part,
c59b13
      minor version number, should be greater than the minor version number
c59b13
      of the kernel version provided in the configuration option, or the first
c59b13
      two parts should be equal and the third part, patch level, should
c59b13
      be greater or equal the patch level of the version in the configuration
c59b13
      option).
c59b13
    * A.B.C-Y (where A, B, C, and Y are decimal numbers), "Y-stream version".
c59b13
      In this case, A.B.C part should be equal, and Y part of the running kernel
c59b13
      version should be greater or equal than the Y part of the configuration
c59b13
      option version in order to satisfy the comparison requirement.
c59b13
    * A.B.C-Y.Z1.Z2 (where A, B, C, Y, Z1, and Z2 are decimal numbers),
c59b13
      "Z-stream version". In this case, A.B.C-Y part should be equal and Z1.Z2
c59b13
      part of the running kernel should be greater or equal than the respective
c59b13
      part of the configuration option version (when compared as a version)
c59b13
      for comparison to succeed.
c59b13
   Kernel version check passed if at least one comparison of the running kernel
c59b13
   version against a kernel version provided in a configuration option
c59b13
   succeeded.  The "kernel" configuration option can be provided
c59b13
   in the configuration file multiple times.
c59b13
 * "kernel_early" is a minimal kernel version that supports proper handling
c59b13
   of the related microcode during early microcode load. The format of the
c59b13
   option and its semantics is similar to the "kernel" configuration options.
c59b13
   This option can be provided multiple times as well.
c59b13
 * "mc_min_ver_late" is the minimal version of the currently loaded microcode
c59b13
   on the CPU (as reported in /proc/cpuinfo) that supports late microcode
c59b13
   update.  Microcode update will be attempted only if the currently loaded
c59b13
   microcode version is greater or equal the microcode version provided
c59b13
   in the configuration option. Can be set in the configuration file only once.
c59b13
 * "disable" is a way to disable a specific caveat from inside its
c59b13
   configuration. Argument for the argument is a list of stages ("early",
c59b13
   "late") for which the caveat should be disable. The configuration option
c59b13
   can be provided multiple times in a configuration file.
3a6b56
 * "pci_config_val" performs check for specific values in selected parts
3a6b56
   of configuration space of specified PCI devices.  If "-m" option
3a6b56
   is not specified, then the actual check is skipped, and the check returns
3a6b56
   result in accordance with the provided "mode" option (se below).  Check
3a6b56
   arguments are a white-space-separated list of "key=value" pairs.
3a6b56
   The following keys are supported:
3a6b56
    * "domain" - PCI domain number, or "*" (an asterisk) for any domain.
3a6b56
      Default is "*".
3a6b56
    * "bus" - PCI bus number, or "*" (an asterisk) for any bus.  Default is "*".
3a6b56
    * "device" - PCI device number, or "*" (an asterisk) for any device.
3a6b56
      Default is "*".
3a6b56
    * "function" - PCI function number, or "*" (an asterisk) for any function.
3a6b56
      Default is "*".
3a6b56
    * "vid" - PCI vendor ID, or empty string for any vendor ID.  Default
3a6b56
      is empty string.
3a6b56
    * "did" - PCI device ID, or empty string for any device ID.  Default
3a6b56
      is empty string.
3a6b56
    * "offset" - offset in device's configuration space where the value resides.
3a6b56
      Default is 0.
3a6b56
    * "size" - field size.  Possible values are 1, 2, 4, or 8.  Default is 4.
3a6b56
    * "mask" - mask applied to the values during the check.  Default is 0.
3a6b56
    * "val" - comma-separated list of matching values.  Default is 0.
3a6b56
    * "mode" - check mode, the way matches are interpreted:
3a6b56
       * "success-any" - check succeeds if there was at least one match,
3a6b56
         otherwise it fails.
3a6b56
       * "success-all" - check succeeds if there was at least one device checked
3a6b56
         and all the checked devices have matches, otherwise the check fails.
3a6b56
       * "fail-any" - check fails if there was at least one match, otherwise
3a6b56
         it succeeds.
3a6b56
       * "fail-all" - check fails if there was at least one device checked
3a6b56
         and all the checked devices have matches, otherwise the check succeeds.
6e6257
      Default is "success-any".
3a6b56
   An example of a check:
3a6b56
       pci_config_val mode=success-all device=30 function=3 vid=0x8086 did=0x2083 offset=0x84 size=4 mask=0x38 val=0x38,0x18,0x8
3a6b56
   It interprets 4 bytes at offset 0x84 of special files "config" under
3a6b56
   directories that match glob pattern "/sys/bus/pci/devices/*:*:1e.3"
3a6b56
   as an unsigned integer value, applies mask 0x38 (thus selecting bit 5..3
3a6b56
   of it) and checks whether it is one of the values 0x38, 0x18, or 0x8 (0b111,
3a6b56
   0b011, or 0b001 in bits 5..3, respectively); if there are such files,
3a6b56
   and all the checked values in every checked file has matched at least one
3a6b56
   of the aforementioned value, then the check is successful, otherwise
3a6b56
   it fails (in accordance with "mode=success-all" semantics).  This check fails
3a6b56
   if "-m" option is not specified.
6e6257
 * "dmi" performs checks for specific values available in DMI sysfs files
ca7245
   (present under /sys/devices/virtual/dmi/id/).  The check (when it is actually
ca7245
   performed; see a not about "no-model-mode" below) fails if one of the files
ca7245
   is not readable.  If "-m" option is not specified, then the actual check
6e6257
   is skipped, and the check returns value in accordance with "no-model-mode"
6e6257
   parameter value (see below).  Check arguments are a white-space-separated
6e6257
   list of "key=value" pairs.  The following keys are supported:
6e6257
    * "key" - DMI file to check. Value can be one of the following: bios_date,
6e6257
      bios_vendor, bios_version, board_asset_tag, board_name, board_serial,
6e6257
      board_vendor, board_version, chassis_asset_tag, chassis_serial,
6e6257
      chassis_type, chassis_vendor, chassis_version, product_family,
6e6257
      product_name, product_serial, product_uuid, product_version, sys_vendor.
6e6257
      Default is empty string.
ca7245
    * "val" - a string to match DMI data present in "key" against.
ca7245
      Can be enclosed in single or double quotes.  Default is empty string.
ca7245
    * "keyval" - a pair of "key" and "val" values (with semantics described
ca7245
      above), separated with either "=", ":", "!=", or "!:" characters.  Enables
ca7245
      providing of multiple key-value pairs by means of supplying multiple
ca7245
      keyval= parameters.  The exclamation sign ("!") character in separator
ca7245
      enables negated matching (so, non-equality of the value in DMI "key" file
ca7245
      and the value of "val" is).  The match considered successful when all
ca7245
      the key/val (non-)equalities are in effect.  This parameter works
ca7245
      in addition to the pair provided in "key" and "val" parameters
ca7245
      (but allows to avoid using them).  Default is empty.
ca7245
    * "mode" - check mode, the way successful matches are interpreted:
6e6257
       * "success-equal" - returns 0 if the value present in the file
6e6257
         with the name supplied via the "key" parameter file under
6e6257
	 /sys/devices/virtual/dmi/id/ is equal to the value supplied as a value
ca7245
	 of "val" parameter and all the pairs provided in "keyval" parameters
ca7245
	 are equal and non-equal in accordance with their definition,
ca7245
	 otherwise 1.
ca7245
       * "fail-equal" - returns 1 if the value present in the file
6e6257
         with the name supplied via the "key" parameter file under
6e6257
	 /sys/devices/virtual/dmi/id/ is equal to the value supplied as a value
ca7245
	 of "val" parameter and all the pairs provided in "keyval" parameters
ca7245
	 are equal and non-equal in accordance with their definition,
ca7245
	 otherwise 0.
6e6257
      Default is "success-any".
6e6257
    * "no-model-mode" - return value if model filter ("-m" option)
6e6257
      is not enabled:
6e6257
       * "success" - return 0.
6e6257
       * "fail" - return 1.
6e6257
      Default is "success".
6e6257
   An example of a check:
6e6257
       dmi mode=fail-equal no-model-mode=success key=bios_vendor val="Dell Inc."
6e6257
   It checks file /sys/devices/virtual/dmi/id/bios_vendor and fails if its
6e6257
   content is "Dell Inc." (without quotes).  It succeeds if "-m" option
6e6257
   is not enabled.
ca7245
   Another example:
ca7245
       dmi mode=fail-equal keyval="sys_vendor=Amazon EC2" keyval="product_name=u-18tb1.metal"
ca7245
       dmi mode=fail-equal keyval="sys_vendor=Lenovo" keyval="product_name=ThinkSystem SR950"
ca7245
   It blocks the caveat from using when either both
ca7245
   /sys/devices/virtual/dmi/id/sys_vendor contains the string "Amazon EC2"
ca7245
   and /sys/devices/virtual/dmi/id/product_name contains the string
ca7245
   "u-18tb1.metal" or both /sys/devices/virtual/dmi/id/sys_vendor contains
ca7245
   the string "Lenovo" and /sys/devices/virtual/dmi/id/product_name contains
ca7245
   the string "ThinkSystem SR950", but enables caveat loading for other products
ca7245
   with the aforementioned /sys/devices/virtual/dmi/id/sys_vendor values,
ca7245
   for example.
ca7245
 * "dependency" allows conditional enablement of a caveat based on the check
ca7245
   status of some other caveat(s).  It has the following format:
ca7245
       dependency DEPENDENCY_TYPE DEPENDENCY_NAME [OPTION...]
ca7245
   where DEPENDENCY_NAME is the configuration to be checked, OPTIONs
ca7245
   are per-DEPENDENCY_TYPE, and the only DEPENDENCY_TYPE that is supported
ca7245
   currently is "required".
ca7245
   Options for the "required" dependency type:
ca7245
    * "match-model-mode" - whether model matching mode ("-m" option)
ca7245
      has to be used for the nested configuration check. Possible values:
ca7245
       * "on" - model-matching mode is always used during the nested check;
ca7245
       * "off" - model-matching mode is never used during the nested check;
ca7245
       * "same" - used the same model-matching mode as it is now.
ca7245
      Default is "same".
ca7245
    * "skip" - controls result of the check when the nested check indicated
ca7245
      skipping of the configuration.
ca7245
       * "fail" - the dependent check fails;
ca7245
       * "success" - the dependent check succeeds;
ca7245
       * "skip" - the dependent check indicates that the configuration
ca7245
         is to be skipped.
ca7245
      Default is "skip".
ca7245
    * "force-skip" - controls result of the check when the nested check
ca7245
      indicated skipping of the configuration caused by the presence
ca7245
      of an override file (see "check_caveats script" section for details).
ca7245
       * "fail" - the dependent check fails;
ca7245
       * "success" - the dependent check succeeds;
ca7245
       * "skip" - the dependent check indicates that the configuration
ca7245
         is to be skipped.
ca7245
      Default is "skip".
ca7245
    * "nesting-too-deep" - as a measure against dependency loop, configuration
ca7245
      checking logic implements nesting limit on dependency checks (currently
ca7245
      set at 8).  This option controls the behaviour of the check
ca7245
      when the nested check cannot be performed due to this limit.
ca7245
       * "fail" - the dependent check fails;
ca7245
       * "success" - the dependent check succeeds;
ca7245
       * "skip" - the dependent check indicates that the configuration
ca7245
         is to be skipped.
ca7245
      Default is "fail".
ca7245
   An example of a check:
ca7245
       dependency required intel skip=success match-model-mode=off
ca7245
   It checks "intel" caveat configuration (see the "Early microcode load
ca7245
   inside a virtual machine" section) with model-matching mode being disabled,
ca7245
   treats skipping of the configuration as a success (unless the configuration
ca7245
   is forced to be skipped, in that case the dependent configuration
ca7245
   is to be skipped as well).
c59b13
c59b13
c59b13
check_caveats script
c59b13
--------------------
c59b13
"check_caveats" is an utility script (called by update_ucode, reload_microcode,
c59b13
dracut module) that performs checks of the target kernel (and running CPU)
c59b13
in accordance with caveat configuration files in directory
c59b13
"/usr/share/microcode_ctl/ucode_with_caveats", and returns information, whether
c59b13
the system passes the checks, or not.
c59b13
c59b13
Usage:
c59b13
    check_caveats [-e] [-k TARGET_KVER] [-c CONFIG]* [-m] [-v]'
c59b13
c59b13
Options:
c59b13
  -e - check for early microcode load possibility (instead of late microcode
c59b13
       load). "kernel_early" caveat configuration options are used for checking
c59b13
       instead of "kernel", and "mc_min_ver_late" is not checked.
c59b13
  -k - target kernel version to check against, $(uname -r) is used otherwise.
c59b13
  -c - caveat(s) to check, all caveat configurations found inside
c59b13
       $MC_CAVEATS_DATA_DIR are checked otherwise.
c59b13
  -m - ignore caveats that do not apply to the current CPU model.
c59b13
  -v - verbose output.
c59b13
c59b13
Environment:
c59b13
  MC_CAVEATS_DATA_DIR - directory that contains caveats configurations,
c59b13
                        "/usr/share/microcode_ctl/ucode_with_caveats"
c59b13
			by default.
c59b13
  FW_DIR - directory containing firmware files (per-kernel configuration
c59b13
           overrides are checked there), "/lib/firmware" by default.
c59b13
  CFG_DIR - directory containing global caveats overrides,
c59b13
            "/etc/microcode_ctl/ucode_with_caveats" by default.
c59b13
c59b13
Output:
c59b13
  Script returns information about caveats check results. Output has a format
c59b13
  of "KEY VALUE1 VALUE2 ..." with KEY defining the semantics of the VALUEs.
c59b13
  Currently, the following data is issued:
c59b13
   - "cfgs" - list of caveats that have been processed (and not skipped
c59b13
      due to missing "config", "readme", or a disallow-* override described
c59b13
      below);
c59b13
   - "skip_cfgs" - list of caveats that have been skipped (due to missing
c59b13
     config/readme file, or because of overrides);
c59b13
   - "paths" - list of glob patterns matching files associated with caveats
c59b13
     that have been processed;
c59b13
   - "ok_cfgs" - list of caveat configurations that have all the checks passed
c59b13
     (or have enforced by one of force-* overrides described below);
c59b13
   - "ok_paths" - list of glob patterns associated with caveat files from
c59b13
     the "ok_cfgs" list;
c59b13
   - "fail_cfgs" - list of caveats that have one of the checks failed.
c59b13
   - "fail_paths" - list of glob patterns associated with caveats from the
c59b13
     "fail_cfgs" list.
c59b13
c59b13
Return value:
c59b13
  - 0 in case caveats check has passed, 1 otherwise.
c59b13
  - In "-d" mode, 0 is always returned.
c59b13
c59b13
Overrides:
c59b13
c59b13
When check_caveats perform its checks, it also checks for presence of files
c59b13
in specific places, and, if they exist, check_caveats skips a caveat or ignores
c59b13
its checks; that mechanism allows overriding the information provided
c59b13
in configuration on local systems and affect the behaviour of the microcode
c59b13
update process.
c59b13
c59b13
Current list of overrides (where $FW_DIR and $CFG_DIR are the environment
c59b13
options described earlier; $kver - the currently processed kernel version,
c59b13
$s is the requested stage ("early" or "late"), $cfg is the caveat directory
c59b13
name):
c59b13
    $FW_DIR/$kver/disallow-$s-$cfg - skip a caveat for the requested stage for
c59b13
                                     a specific kernel version..
c59b13
    $FW_DIR/$kver/force-$s-$cfg - apply a specific caveat file for a specific
c59b13
                                  kernel version for the requested stage without
c59b13
				  performing any checks.
c59b13
    $FW_DIR/$kver/disallow-$cfg - skip a caveat for any stage for a specific
c59b13
                                  kernel version.
c59b13
    $FW_DIR/$kver/force-$cfg - apply a specific caveat for any stage
c59b13
                               for a specific kernel version without checks.
c59b13
    $FW_DIR/$kver/disallow-$s - skip all caveats for a specific stage
c59b13
                                for a specific kernel version.
c59b13
    $CFG_DIR/disallow-$s-$cfg - skip a caveat for a specific stage for all
c59b13
                                kernel versions.
c59b13
    $FW_DIR/$kver/force-$s - apply all caveats for a specific stage
c59b13
                             for a specific kernel version without checks.
c59b13
    $CFG_DIR/force-$s-$cfg - apply a specific caveat for a specific stage for
c59b13
                             all kernel versions without checks.
c59b13
    $FW_DIR/$kver/disallow - skip all caveats for all stages for a specific
c59b13
                             kernel version.
c59b13
    $CFG_DIR/disallow-$cfg - skip a caveat for all stages for all kernel
c59b13
                             versions.
c59b13
    $FW_DIR/$kver/force - apply all caveats for all stages for a specific kernel
c59b13
                          version without checks.
c59b13
    $CFG_DIR/force-$cfg - apply a caveat for all stages for all kernel versions
c59b13
                          without checks.
c59b13
    $CFG_DIR/disallow-$s - skip all caveat for all kernel versions
c59b13
                           for a specific stage.
c59b13
    $CFG_DIR/force-$s - apply all caveats for all kernel versions for  specific
c59b13
                        stage without checks.
c59b13
    $CFG_DIR/disallow - skip all caveats for all stages for all kernel versions
c59b13
                        (disable everything).
c59b13
    $CFG_DIR/force - force all caveats for all stages for all kernel versions
c59b13
                     (enable everything).
c59b13
c59b13
The "apply" action above means creating symlinks in /lib/firmware by
c59b13
update_ucode in case of the "late" stage and adding caveat directory to the list
c59b13
of firmware directories by dracut plugin in case of the "early" stage.
c59b13
c59b13
The files are checked for existence until the first match, so more specific
c59b13
overrides can override more broad ones.
c59b13
c59b13
Also, a caveat is ignored if it lacks either config or readme file.
c59b13
c59b13
c59b13
update_ucode script
c59b13
-------------------
c59b13
"update_ucode" populates symlinks to microcode files in accordance with caveats
c59b13
configuration.  It enables late microcode loading that is invoked by triggering
c59b13
/sys/devices/system/cpu/microcode/reload file.  Since caveats depend
c59b13
on the kernel version, symlinks are populated inside
c59b13
"/lib/firmware/KERNEL_VERSION" directory for each installed kernel.
c59b13
As a consequence, this script is triggered upon each kernel package installation
c59b13
and removal.
c59b13
c59b13
The script has two parts: common and kernel-version-specific.
c59b13
c59b13
During the common part, files are populated from
c59b13
/usr/share/microcode_ctl/intel-ucode in /lib/firmware/intel-ucode. There are
c59b13
several possibilities to affect the process:
c59b13
 * Presence of "/etc/microcode_ctl/intel-ucode-disallow" file leads to skipping
c59b13
   the common part of the script.
c59b13
 * The same for "/lib/firmware/intel-ucode-disallow".
c59b13
c59b13
During the kernel-version-specific part, each caveat is checked against every
c59b13
kernel version, and those combinations, for which caveat check succeeds,
c59b13
gets the symlinks to the associated microcode files populated.
c59b13
 * Absence of "/lib/firmware/KERNEL_VERSION/readme-CAVEAT" prevents update_ucode
c59b13
   from removing symlinks related to the caveat for specific kernel version.
c59b13
 * Since the check is being done by check_caveats, all the overrides that
c59b13
   described there also stay.
c59b13
c59b13
Usage:
c59b13
    update_ucode [--action {add|remove|refresh|list}] [--kernel KERNELVER]*
c59b13
                 [--verbose] [--dry-run] [--cleanup intel_ucode caveats_ucode]
c59b13
                 [--skip-common] [--skip-kernel-specific]
c59b13
c59b13
Options:
c59b13
  --action - action to perform. Currently, the following actions are supported:
c59b13
              * "add" - create new symlinks.
c59b13
              * "remove" - remove old symlinks that are no longer needed.
c59b13
              * "refresh" - re-populate symlinks.
c59b13
              * "list" - list files under control of update_ucode.
c59b13
             By default, "refresh" action is executed.
c59b13
  --kernel - kernel version to process. By default, list of kernel versions
c59b13
             is formed based on contents of /lib/firmware and /lib/modules
c59b13
             directories.
c59b13
  --verbose - verbose output.
c59b13
  --dry-run - do not call commands, just print the invocation lines.
c59b13
  --cleanup - cleanup mode. Used by post-uninstall script during package
c59b13
              upgrades. Removes excess files in accordance to the contents
c59b13
              of the files provided in the arguments to the option.
c59b13
  --skip-common - do not process /lib/firmware directory.
c59b13
  --skip-kernel-specific - do not process /lib/firmware/KERNEL_VERSION
c59b13
                           directories.
c59b13
c59b13
Return value:
c59b13
  0 on success, 1 on error.
c59b13
c59b13
c59b13
reload_microcode script
c59b13
-----------------------
c59b13
"reload_microcode" is a script that is called by microcode.service and
c59b13
triggers late microcode reloading (by writing "1" to
c59b13
/sys/devices/system/cpu/microcode/reload) if the following check are passed:
c59b13
 * the microcode update performed not in a virtualised environment;
c59b13
 * running kernel passes "check_caveats" checks that applicable to the current
c59b13
   CPU model.
c59b13
c59b13
For a virtualised environment check, the script searches the "/proc/cpuinfo"
c59b13
file for presence of the "hypervisor" flag among CPU features (it corresponds
c59b13
to a CPUID feature bit set by hypervisors in order to inform that the kernel
c59b13
operates inside a virtual machine).  This check can be overridden and skipped
c59b13
by creation of a file "/etc/microcode_ctl/ignore-hypervisor-flag".
c59b13
c59b13
The script has no options and always returns 0.
c59b13
c59b13
c59b13
99microcode_ctl-fw_dir_override dracut module
c59b13
---------------------------------------------
c59b13
This dracut module injects directories with microcode files for caveats
c59b13
that pass "early" check_caveats check (with "-e" flag). In addition
c59b13
to "check_caveats" overrides, the following abilities to control module's
c59b13
behaviour are present:
c59b13
 * Presence of one of the following files:
c59b13
   - /etc/microcode_ctl/ucode_with_caveats/skip-host-only-check
c59b13
   - /etc/microcode_ctl/ucode_with_caveats/skip-host-only-check-$cfg
c59b13
   - /lib/firmware/$kver/skip-host-only-check
c59b13
   - /lib/firmware/$kver/skip-host-only-check-$cfg
c59b13
   (where "$kver" is the kernel version in question and "$cfg" is the caveat
c59b13
   directory name) allows skipping matching of microcode file name when dracut's
c59b13
   Host-Only mode is enabled.
c59b13
c59b13
When caveats_check succeeds, caveats directory (not its possibly populated
c59b13
version for late microcode update: "/lib/firmware/KERNEL_VERSION";
c59b13
it is done so in order
c59b13
to have ability to configure list of caveats enabled for early and late
c59b13
microcode update, independently) is added to dracut's list of firmware search
c59b13
directories.
c59b13
c59b13
The module can be disabled by running dracut with
c59b13
"-o microcode_ctl-fw_dir_override" (for one-time exclusion), or it can
c59b13
be disabled permanently by uncommenting string
c59b13
"omit_dracutmodules+=' microcode_ctl-fw_dir_override '" in
c59b13
/usr/lib/dracut/dracut.conf.d/99-microcode-override.conf configuration file.
c59b13
c59b13
See dracut(8), section "Omitting dracut Modules", and dracut.conf(5), variable
c59b13
"omit_dracutmodules" for additional information.
c59b13
c59b13
c59b13
Caveats
c59b13
=======
c59b13
c59b13
Intel Broadwell-EP/EX ("BDX-ML B/M/R0") caveat
c59b13
----------------------------------------------
c59b13
Microcode update process on Intel Broadwell-EP/EX CPUs (BDX-ML B/M/R0,
c59b13
family 6, model 79, stepping 1) has issues that lead to system instability.
c59b13
A series of changes for the Linux kernel has been developed in order to work
c59b13
around those issues; however, as it turned out, some systems have issues even
c59b13
when a microcode update performed on a kernel that contains those changes.
c59b13
As a result, microcode update for this CPU model is disabled by default;
c59b13
the microcode file, however, is still shipped as a part of microcode_ctl
c59b13
package and can be used for performing a microcode update if it is enforced
078ac8
via the aforementioned overrides. (See the sections "check_caveats script"
078ac8
and "reload_microcode script" for details.)
078ac8
078ac8
Caveat name: intel-06-4f-01
c59b13
c59b13
Affected microcode: intel-ucode/06-4f-01.
c59b13
ca7245
Dependencies: intel
ca7245
c59b13
Mitigation: microcode loading is disabled for the affected CPU model.
c59b13
c59b13
Minimum versions of the kernel package that contain the aforementioned patch
c59b13
series:
c59b13
 - Upstream/RHEL 8: 4.17.0
c59b13
 - RHEL 7.6 onwards:  3.10.0-894
c59b13
 - RHEL 7.5:  3.10.0-862.6.1
c59b13
 - RHEL 7.4:  3.10.0-693.35.1
c59b13
 - RHEL 7.3:  3.10.0-514.52.1
c59b13
 - RHEL 7.2:  3.10.0-327.70.1
c59b13
 - RHEL 6.10: 2.6.32-754.1.1
c59b13
 - RHEL 6.7:  2.6.32-573.58.1
c59b13
 - RHEL 6.6:  2.6.32-504.71.1
c59b13
 - RHEL 6.5:  2.6.32-431.90.1
c59b13
 - RHEL 6.4:  2.6.32-358.90.1
c59b13
c59b13
c59b13
Early microcode load inside a virtual machine
c59b13
---------------------------------------------
c59b13
RHEL 8 kernel supports performing microcode update during early boot stage
c59b13
from a cpio archive placed at the beginning of the initramfs image.  However,
c59b13
when an early microcode update is attempted inside some virtualised
c59b13
environments, that may result in unexpected system behaviour.
c59b13
078ac8
Caveat name: intel
078ac8
c59b13
Affected microcode: all.
c59b13
ca7245
Dependencies: (none)
ca7245
078ac8
Mitigation: early microcode loading is disabled for all CPU models on kernels
078ac8
without the fix.
c59b13
c59b13
Minimum versions of the kernel package that contain the fix:
c59b13
 - Upstream/RHEL 8: 4.10.0
c59b13
 - RHEL 7.6 onwards: 3.10.0-930
c59b13
 - RHEL 7.5: 3.10.0-862.14.1
c59b13
 - RHEL 7.4: 3.10.0-693.38.1
c59b13
 - RHEL 7.3: 3.10.0-514.57.1
c59b13
 - RHEL 7.2: 3.10.0-327.73.1
c59b13
c59b13
078ac8
Intel Sandy Bridge-E/EN/EP caveat
078ac8
---------------------------------
6e6257
Microcode revision 0x718 for Intel Sandy Bridge-E/EN/EP (SNB-EP, family 6,
6e6257
model 45, stepping 7), that was released to address MDS vulnerability,
6e6257
and was available from microcode-20190618 up to microcode-20190508 release)
6e6257
could lead to system instability[1][2].  In order to address this,
6e6257
this microcode update was not used and the previous microcode revision
6e6257
was provided instead by default; the microcode file, however, was still shipped
6e6257
as part of microcode_ctl package and could be used for performing a microcode
6e6257
update if it is enforced via the aforementioned overrides.  With the release
6e6257
of 0x71a revision of the microcode (as art of microcode-20200520 release)
6e6257
that aims at fixing the aforementioned stability issue, the latest microcode
6e6257
revision is again used by default; it is still provided via the caveat
6e6257
mechanism, hovewer, in order to enable ability to disable it in case such
6e6257
a need arises.  (See the sections "check_caveats script" and "reload_microcode
6e6257
script" for details regarding caveats mechanism operation.)
078ac8
3a6b56
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/15
3a6b56
[2] https://access.redhat.com/solutions/4593951
3a6b56
078ac8
Caveat name: intel-06-2d-07
078ac8
078ac8
Affected microcode: intel-ucode/06-2d-07.
078ac8
ca7245
Dependencies: intel
ca7245
6e6257
Mitigation: None; the latest revision of the microcode file is used by default;
6e6257
previously published microcode revision 0x714 is still available as a fallback
6e6257
as part of "intel" caveat.
078ac8
078ac8
078ac8
Intel Skylake-SP/W/X caveat
078ac8
---------------------------
6e6257
Microcode revision 0x2000065 (that was provided with microcode releases
6e6257
microcode-20191112 up to microcode-20200520) for some CPU models that belong
6e6257
to Intel Skylake Scalable Platform (SKL-W/X, family 6, model 85, stepping 4,
6e6257
Workstation/HEDT segments) could lead to hangs during reboot[1].  In order
6e6257
to address this, by default this microcode update was disabled by default and
6e6257
and the previous 0x2000064 microcode revision was used instead; the microcode
6e6257
file with, however, is still shipped as part of microcode_ctl package and can
6e6257
be used for performing a microcode update if it is enforced
6e6257
via the aforementioned overrides. With the availability of 0x2006906 revision
6e6257
of the microcode (in the microcode-20200609 release) that fixes
6e6257
the aforementioned issue, the latest microcode revision is again used
6e6257
by default; it is still provided via caveat mechanism, hovewer, in order
6e6257
to enable ability to disable it in case such a need arises.  (See the sections
6e6257
"check_caveats script" and "reload_microcode script" for details regarding
6e6257
caveats mechanism operation.)
3a6b56
3a6b56
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/21
078ac8
078ac8
Caveat name: intel-06-55-04
078ac8
078ac8
Affected microcode: intel-ucode/06-55-04.
078ac8
ca7245
Dependencies: intel
ca7245
6e6257
Mitigation: None; the latest revision of the microcode file is used by default;
6e6257
previously published microcode revision 0x2000064 is still available
6e6257
as a fallback as part of "intel" caveat.
6e6257
6e6257
ca7245
Intel Skylake-U/Y caveat
ca7245
------------------------
ca7245
Some Intel Skylake CPU models (SKL-U/Y, family 6, model 78, stepping 3)
ca7245
have reports of system hangs when revision 0xdc of microcode, that is included
ca7245
in microcode-20200609 update to address CVE-2020-0543, CVE-2020-0548,
ca7245
and CVE-2020-0549, is applied[1].  In order to address this, microcode update
ca7245
to the newer revision has been disabled by default on these systems,
ca7245
and the previously published microcode revision 0xd6 is used instead; the newer
ca7245
microcode files, however, are still shipped as part of microcode_ctl package
ca7245
and can be used for performing a microcode update if they are enforced
ca7245
via the aforementioned overrides.  (See the sections "check_caveats script"
ca7245
and "reload_microcode script" for details.)
6e6257
6e6257
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31
6e6257
ca7245
Caveat name: intel-06-4e-03
6e6257
ca7245
Affected microcode: intel-ucode/06-4e-03
ca7245
ca7245
Dependencies: intel
6e6257
6e6257
Mitigation: previously published microcode revision 0xd6 is used by default.
6e6257
6e6257
ca7245
Intel Skylake-H/S/Xeon E3 v5 caveat
ca7245
-----------------------------------
ca7245
Some Intel Skylake CPU models (SKL-H/S/Xeon E3 v5, family 6, model 94,
ca7245
stepping 3) had reports of system hangs when revision 0xdc of microcode,
ca7245
that is included in microcode-20200609 update to address CVE-2020-0543,
ca7245
CVE-2020-0548, and CVE-2020-0549, was applied[1].  In order to address this,
ca7245
microcode update to the newer revision had been disabled by default on these
ca7245
systems, and the previously published microcode revision 0xd6 was used instead.
ca7245
The revision 0xea seems[2] to have fixed the aforementioned issue, hence
ca7245
the latest microcode revision usage it is enabled by default,
ca7245
but can be disabled explicitly via the aforementioned overrides.  (See
ca7245
the sections "check_caveats script" and "reload_microcode script" for details.)
ca7245
ca7245
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-644885826
ca7245
[2] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-857806014
ca7245
ca7245
Caveat names: intel-06-5e-03
ca7245
ca7245
Affected microcode: intel-ucode/06-5e-03.
ca7245
ca7245
Dependencies: intel
ca7245
ca7245
Mitigation: None; the latest revision of the microcode file is used by default;
ca7245
previously published microcode revision 0xd6 is still available as a fallback
ca7245
as part of "intel" caveat.
ca7245
ca7245
6e6257
Dell caveats
6e6257
------------
6e6257
Some Dell systems that use some models of Intel CPUs are susceptible to hangs
6e6257
and system instability during or after microcode update to revision 0xc6/0xca
6e6257
(included as part of microcode-20191113/microcode-20191115 update that addressed
6e6257
CVE-2019-0117, CVE-2019-0123, CVE-2019-11135, and CVE-2019-11139)
6e6257
and/or revision 0xd6 (included as part of microcode-20200609 update
6e6257
that addressed CVE-2020-0543, CVE-2020-0548, and CVE-2020-0549)
6e6257
[1][2][3][4][5][6].  In order to address this, microcode update to the newer
6e6257
revision has been disabled by default on these systems, and the previously
6e6257
published microcode revisions 0xae/0xb4/0xb8 are used by default
6e6257
for the OS-driven microcode update.
6e6257
6e6257
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/23
6e6257
[2] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/24
6e6257
[3] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/33
6e6257
[4] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/34
6e6257
[5] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/35
6e6257
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1846097
6e6257
6e6257
Caveat names: intel-06-8e-9e-0x-dell, intel-06-8e-9e-0x-0xca
6e6257
6e6257
Affected microcode: intel-ucode/06-8e-09, intel-ucode/06-8e-0a,
6e6257
                    intel-ucode/06-8e-0b, intel-ucode/06-8e-0c,
6e6257
                    intel-ucode/06-9e-09, intel-ucode/06-9e-0a,
6e6257
                    intel-ucode/06-9e-0b, intel-ucode/06-9e-0c,
6e6257
                    intel-ucode/06-9e-0d.
6e6257
ca7245
Dependencies: intel
ca7245
6e6257
Mitigation: previously published microcode revision 0xac/0xb4/0xb8 is used
6e6257
            by default if /sys/devices/virtual/dmi/id/bios_vendor reports
6e6257
	    "Dell Inc."; otherwise, the latest microcode revision is used.
6e6257
	    Caveat with revision 0xca of microcode files is provided
6e6257
	    as a convenience for the cases where it was working well before.
078ac8
078ac8
96af4f
Intel Tiger Lake-UP3/UP4 caveat
96af4f
-------------------------------
96af4f
Some systems with Intel Tiger Lake-UP3/UP4 CPUs (TGL, family 6, model 140,
ca7245
stepping 1) had reports of system hangs when a microcode update,
ca7245
that was included since microcode-20201110 release, was applied[1].
ca7245
In order to address this, microcode update to a newer revision had been disabled
ca7245
by default on these systems.  The revision 0x88 seems to have fixed
ca7245
the aforementioned issue, hence it is enabled by default; however, it is still
ca7245
can be disabled via the aforementioned overrides.  (See the sections
96af4f
"check_caveats script" and "reload_microcode script" for details.)
96af4f
96af4f
[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/44
96af4f
96af4f
Caveat names: intel-06-8c-01
96af4f
96af4f
Affected microcode: intel-ucode/06-8c-01.
96af4f
ca7245
Dependencies: intel
ca7245
ca7245
Mitigation: None; the latest revision of the microcode file is used by default.
96af4f
96af4f
078ac8
c59b13
Additional information
c59b13
======================
078ac8
Red Hat provides updated microcode, developed by its microprocessor partners,
078ac8
as a customer convenience.  Please contact your hardware vendor to determine
078ac8
whether more recent BIOS/firmware updates are recommended because additional
078ac8
improvements may be available.
c59b13
c59b13
Information regarding microcode revisions required for mitigating specific
078ac8
Intel CPU vulnerabilities is available in the following knowledge base articles:
c59b13
 * CVE-2017-5715 ("Spectre"):
c59b13
   https://access.redhat.com/articles/3436091
c59b13
 * CVE-2018-3639 ("Speculative Store Bypass"):
c59b13
   https://access.redhat.com/articles/3540901
c59b13
 * CVE-2018-3620, CVE-2018-3646 ("L1 Terminal Fault Attack"):
c59b13
   https://access.redhat.com/articles/3562741
c59b13
 * CVE-2018-12130, CVE-2018-12126, CVE-2018-12127, and CVE-2019-11091
c59b13
   ("Microarchitectural Data Sampling"):
c59b13
   https://access.redhat.com/articles/4138151
078ac8
 * CVE-2019-0117 (Intel SGX Information Leak),
078ac8
   CVE-2019-0123 (Intel SGX Privilege Escalation),
078ac8
   CVE-2019-11135 (TSX Asynchronous Abort),
078ac8
   CVE-2019-11139 (Voltage Setting Modulation):
078ac8
   https://access.redhat.com/solutions/2019-microcode-nov
6e6257
 * CVE-2020-0543 (Special Register Buffer Data Sampling),
6e6257
   CVE-2020-0548 (Vector Register Data Sampling),
6e6257
   CVE-2020-0549 (L1D Cache Eviction Sampling):
6e6257
   https://access.redhat.com/solutions/5142751
96af4f
 * CVE-2020-8695 (Information disclosure issue in Intel SGX via RAPL interface),
96af4f
   CVE-2020-8696 (Vector Register Leakage-Active),
96af4f
   CVE-2020-8698 (Fast Forward Store Predictor):
96af4f
   https://access.redhat.com/articles/5569051
ca7245
 * CVE-2020-24489 (VT-d-related Privilege Escalation),
ca7245
   CVE-2020-24511 (Improper Isolation of Shared Resources),
ca7245
   CVE-2020-24512 (Observable Timing Discrepancy),
ca7245
   CVE-2020-24513 (Information Disclosure on Some Intel Atom Processors):
ca7245
   https://access.redhat.com/articles/6101171
548685
 * CVE-2021-0127 (Intel Processor Breakpoint Control Flow),
548685
   CVE-2021-0145 (Fast store forward predictor - Cross Domain Training),
548685
   CVE-2021-0146 (VT-d-related Privilege Escalation),
548685
   CVE-2021-33120 (Out of bounds read for some Intel Atom processors):
548685
   https://access.redhat.com/articles/6716541
871b4f
 * CVE-2022-0005 (Informational disclosure via JTAG),
871b4f
   CVE-2022-21123 (Shared Buffers Data Read),
871b4f
   CVE-2022-21125 (Shared Buffers Data Sampling),
871b4f
   CVE-2022-21127 (Update to Special Register Buffer Data Sampling),
871b4f
   CVE-2022-21131 (Protected Processor Inventory Number (PPIN) access protection),
871b4f
   CVE-2022-21136 (Overclocking service access protection),
871b4f
   CVE-2022-21151 (Optimization Removal-Induced Informational Disclosure),
871b4f
   CVE-2022-21166 (Device Register Partial Write):
871b4f
   https://access.redhat.com/articles/6963124
bbefcb
 * CVE-2022-21233 (Stale Data Read from legacy xAPIC):
bbefcb
   https://access.redhat.com/articles/6976398