Intel Microcode Vulnerability: Information Disclosure Risk in Ubuntu Packages

intel-microcode Updated 02 Oct 2025

Summary

15/06/2022
N/A
No i
Medium
5.5

UBUNTU-CVE-2022-21127: Incomplete cleanup in specific special register read operations for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. Affects intel-microcode versions 1.20130906.1ubuntu2 – 3.20210608.0ubuntu0.14.04.1+esm1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'intel-microcode' package provides microcode updates for Intel processors, enhancing system stability and performance. It is crucial for ensuring that the CPU operates correctly and securely. This package is particularly important for users running Ubuntu LTS versions, as it helps mitigate hardware vulnerabilities and improve overall system security.

Vulnerability Detail

The vulnerability identified as CVE-2022-21127 involves incomplete cleanup in specific special register read operations for some Intel processors. This flaw could allow an authenticated user to potentially enable information disclosure via local access. The vulnerability poses a risk of exposing sensitive information, which could be exploited by malicious actors with local access to the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the available updates as soon as possible.

Conclusion

The intel-microcode vulnerability (CVE-2022-21127) poses a significant risk of information disclosure for users of affected Ubuntu versions. It is crucial to apply the necessary updates to mitigate this risk. Users can utilize tools like Vulert to monitor and alert for open-source vulnerabilities in their software, ensuring ongoing security.

See every vulnerability recorded for intel-microcode →

Share this vulnerability

FAQ

CVE-2022-21127 is a vulnerability in the intel-microcode package that allows for potential information disclosure due to incomplete cleanup in specific register read operations.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score of this vulnerability is 5.5, indicating a medium severity level.

For Ubuntu 18.04, no subscription is required to access the fixed version of the intel-microcode package.

If you cannot update the package immediately, ensure that you limit local access to the system and monitor for any unusual activity until the update can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for intel-microcode.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback