usn-4628-2
Vulnerability from osv_ubuntu
Published
2020-11-12 01:14
Modified
2026-06-29 10:52
Summary
intel-microcode regression
Details

USN-4628-1 provided updated Intel Processor Microcode. Unfortunately, that update prevented certain processors in the Intel Tiger Lake family from booting successfully. This update reverts the microcode update for the Tiger Lake processor family.

Please note that the 'dis_ucode_ldr' kernel command line option can be added in the boot menu to disable microcode loading for system recovery.

We apologize for the inconvenience.

Original advisory details:

Moritz Lipp, Michael Schwarz, Andreas Kogler, David Oswald, Catherine Easdon, Claudio Canella, and Daniel Gruss discovered that the Intel Running Average Power Limit (RAPL) feature of some Intel processors allowed a side- channel attack based on power consumption measurements. A local attacker could possibly use this to expose sensitive information. (CVE-2020-8695)

Ezra Caltum, Joseph Nuzman, Nir Shildan and Ofir Joseff discovered that some Intel(R) Processors did not properly remove sensitive information before storage or transfer in some situations. A local attacker could possibly use this to expose sensitive information. (CVE-2020-8696)

Ezra Caltum, Joseph Nuzman, Nir Shildan and Ofir Joseff discovered that some Intel(R) Processors did not properly isolate shared resources in some situations. A local attacker could possibly use this to expose sensitive information. (CVE-2020-8698)

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:Pro:14.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "intel-microcode",
            "binary_version": "3.20201110.0ubuntu0.14.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:14.04:LTS",
        "name": "intel-microcode",
        "purl": "pkg:deb/ubuntu/intel-microcode@3.20201110.0ubuntu0.14.04.2?arch=source\u0026distro=trusty/esm"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.20201110.0ubuntu0.14.04.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.20130906.1ubuntu2",
        "1.20130906.1ubuntu3",
        "2.20140122.1",
        "2.20140430.1ubuntu1",
        "2.20140624-t-1ubuntu2",
        "3.20180108.0~ubuntu14.04.2",
        "3.20180108.0+really20170707ubuntu14.04.1",
        "3.20180312.0~ubuntu14.04.1",
        "3.20180425.1~ubuntu0.14.04.1",
        "3.20180425.1~ubuntu0.14.04.2",
        "3.20180807a.0ubuntu0.14.04.1",
        "3.20190514.0ubuntu0.14.04.1",
        "3.20190514.0ubuntu0.14.04.2",
        "3.20190618.0ubuntu0.14.04.1",
        "3.20191112-0ubuntu0.14.04.2",
        "3.20191115.1ubuntu0.14.04.1",
        "3.20191115.1ubuntu0.14.04.2",
        "3.20200609.0ubuntu0.14.04.0",
        "3.20200609.0ubuntu0.14.04.1",
        "3.20201110.0ubuntu0.14.04.1"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:16.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "intel-microcode",
            "binary_version": "3.20201110.0ubuntu0.16.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "intel-microcode",
        "purl": "pkg:deb/ubuntu/intel-microcode@3.20201110.0ubuntu0.16.04.2?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.20201110.0ubuntu0.16.04.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.20150121.1",
        "3.20151106.1",
        "3.20170707.1~ubuntu16.04.0",
        "3.20180108.0~ubuntu16.04.2",
        "3.20180108.0+really20170707ubuntu16.04.1",
        "3.20180312.0~ubuntu16.04.1",
        "3.20180425.1~ubuntu0.16.04.1",
        "3.20180425.1~ubuntu0.16.04.2",
        "3.20180807a.0ubuntu0.16.04.1",
        "3.20190514.0ubuntu0.16.04.1",
        "3.20190514.0ubuntu0.16.04.2",
        "3.20190618.0ubuntu0.16.04.1",
        "3.20191112-0ubuntu0.16.04.2",
        "3.20191115.1ubuntu0.16.04.1",
        "3.20191115.1ubuntu0.16.04.2",
        "3.20200609.0ubuntu0.16.04.0",
        "3.20200609.0ubuntu0.16.04.1",
        "3.20201110.0ubuntu0.16.04.1"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:18.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "intel-microcode",
            "binary_version": "3.20201110.0ubuntu0.18.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "intel-microcode",
        "purl": "pkg:deb/ubuntu/intel-microcode@3.20201110.0ubuntu0.18.04.2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.20201110.0ubuntu0.18.04.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.20170707.1",
        "3.20171117.1",
        "3.20180108.1",
        "3.20180108.1+really20171117.1",
        "3.20180312.0~ubuntu18.04.1",
        "3.20180425.1~ubuntu0.18.04.1",
        "3.20180425.1~ubuntu0.18.04.2",
        "3.20180807a.0ubuntu0.18.04.1",
        "3.20190514.0ubuntu0.18.04.2",
        "3.20190514.0ubuntu0.18.04.3",
        "3.20190618.0ubuntu0.18.04.1",
        "3.20191112-0ubuntu0.18.04.2",
        "3.20191115.1ubuntu0.18.04.1",
        "3.20191115.1ubuntu0.18.04.2",
        "3.20200609.0ubuntu0.18.04.0",
        "3.20200609.0ubuntu0.18.04.1",
        "3.20201110.0ubuntu0.18.04.1"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [],
          "ecosystem": "Ubuntu:20.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "intel-microcode",
            "binary_version": "3.20201110.0ubuntu0.20.04.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "intel-microcode",
        "purl": "pkg:deb/ubuntu/intel-microcode@3.20201110.0ubuntu0.20.04.2?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.20201110.0ubuntu0.20.04.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.20190918.1ubuntu1",
        "3.20191115.1ubuntu1",
        "3.20191115.1ubuntu2",
        "3.20191115.1ubuntu3",
        "3.20200609.0ubuntu0.20.04.0",
        "3.20200609.0ubuntu0.20.04.1",
        "3.20200609.0ubuntu0.20.04.2",
        "3.20201110.0ubuntu0.20.04.1"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-4628-1 provided updated Intel Processor Microcode. Unfortunately,\nthat update prevented certain processors in the Intel Tiger Lake family\nfrom booting successfully. This update reverts the microcode update for\nthe Tiger Lake processor family.\n\nPlease note that the \u0027dis_ucode_ldr\u0027 kernel command line option can be\nadded in the boot menu to disable microcode loading for system recovery.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n Moritz Lipp, Michael Schwarz, Andreas Kogler, David Oswald, Catherine\n Easdon, Claudio Canella, and Daniel Gruss discovered that the Intel Running\n Average Power Limit (RAPL) feature of some Intel processors allowed a side-\n channel attack based on power consumption measurements. A local attacker\n could possibly use this to expose sensitive information. (CVE-2020-8695)\n \n Ezra Caltum, Joseph Nuzman, Nir Shildan and Ofir Joseff discovered that\n some Intel(R) Processors did not properly remove sensitive information\n before storage or transfer in some situations. A local attacker could\n possibly use this to expose sensitive information. (CVE-2020-8696)\n \n Ezra Caltum, Joseph Nuzman, Nir Shildan and Ofir Joseff discovered that\n some Intel(R) Processors did not properly isolate shared resources in some\n situations. A local attacker could possibly use this to expose sensitive\n information. (CVE-2020-8698)\n",
  "id": "USN-4628-2",
  "modified": "2026-06-29T10:52:47Z",
  "published": "2020-11-12T01:14:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-4628-2"
    },
    {
      "type": "REPORT",
      "url": "https://launchpad.net/bugs/1903883"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "intel-microcode regression",
  "upstream": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.