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.

Published: 2022-06-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-21127 is rated Moderate Risk (59.1/100): CVSS Medium severity, with high exploitation likelihood (EPSS 5.51%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +5.04% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-21127

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.47% 5.51% +5.04%
2 2026-04-14 0.28% 0.47% +0.19%
3 2026-03-25 — 0.28% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-21127

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2022-21127

OS Trackers for CVE-2022-21127

vendor priority summary link
alpine — CVE-2022-21127: 1 source package rows (xen); 461 state rows across 8 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 443, open 18. https://security.alpinelinux.org/vuln/CVE-2022-21127
debian not yet assigned CVE-2022-21127 not yet assigned priority: Debian including 1 source packages (intel-microcode), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-21127
redhat medium — https://access.redhat.com/security/cve/CVE-2022-21127
suse medium CVE-2022-21127 severity moderate: SUSE including 404 source package names (cluster-md-kmp-64kb-5.14.21-150400.24.11.1, cluster-md-kmp-64kb-5.3.18-150300.59.71.2, …), 1115 product×package rows across 226 product lines (Container suse/sle-micro-rancher/5.2, Container suse/sle-micro-rancher/5.3, … (226 product lines)): Fixed 1115. https://www.suse.com/security/cve/CVE-2022-21127/
ubuntu medium CVE-2022-21127 medium priority: Ubuntu including 1 source packages (intel-microcode), 8 status rows across 8 suites (bionic, focal, impish, jammy, kinetic, trusty, upstream, xenial): released 7, ignored 1. https://ubuntu.com/security/CVE-2022-21127

Affected software / configurations for CVE-2022-21127

Vendor Product Version Raw CPE
xen xen — cpe:2.3:o:xen:xen:*:*:*:*:*:*:x86:*
intel sgx_dcap < 1.14.100.3 cpe:2.3:a:intel:sgx_dcap:*:*:*:*:*:linux:*:*
intel sgx_dcap < 1.14.100.3 cpe:2.3:a:intel:sgx_dcap:*:*:*:*:*:windows:*:*
intel sgx_psw < 2.16.100.3 cpe:2.3:a:intel:sgx_psw:*:*:*:*:*:windows:*:*
intel sgx_psw < 2.17.100.3 cpe:2.3:a:intel:sgx_psw:*:*:*:*:*:linux:*:*
intel sgx_sdk < 2.16.100.3 cpe:2.3:a:intel:sgx_sdk:*:*:*:*:*:windows:*:*
intel sgx_sdk < 2.17.100.3 cpe:2.3:a:intel:sgx_sdk:*:*:*:*:*:linux:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2022-21127

cvelogic Threat Intelligence