CVE-2022-21127 json
Incomplete cleanup in specific special register read operations for some Intel(R) Processors may allow an authenticated user to potentially…
published 4y ago modified 4mo ago also EUVD-2022-26375
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.5%
- EPSS 5.5% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- intel sgx_dcap 1.14.100.3
- intel sgx_psw 2.16.100.3, 2.17.100.3
- intel sgx_sdk 2.16.100.3, 2.17.100.3
- intel-microcode Debian 14, Debian 13, Debian 12 3.20220510.1
debian advisories DEBIAN-CVE-2022-21127
- intel-microcode Ubuntu 18.04 LTS 3.20220510.0ubuntu0.18.04.1
- intel-microcode Ubuntu 20.04 LTS 3.20220510.0ubuntu0.20.04.1
- intel-microcode Ubuntu 22.04 LTS 3.20220510.0ubuntu0.22.04.1
- intel-microcode Ubuntu Pro 16.04 LTS 3.20220510.0ubuntu0.16.04.1+esm1
ubuntu advisories UBUNTU-CVE-2022-21127
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt SLE Real Time 12 SP5 4.12.14-10.94.1
- kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.94.1
- kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.94.1
- kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.94.1
- kernel-azure SLE Module for Public Cloud 15 SP4, openSUSE Leap 15.4 5.14.21-150400.14.7.1
- kernel-syms-azure SLE Module for Public Cloud 15 SP4, openSUSE Leap 15.4 5.14.21-150400.14.7.1
- kernel-source-azure SLE Module for Public Cloud 15 SP4, openSUSE Leap 15.4 5.14.21-150400.14.7.1
- dtb-aarch64 openSUSE Leap 15.4 5.14.21-150400.24.11.1
suse advisories SUSE-SU-2023:0416-1SUSE-SU-2022:2629-1SUSE-SU-2022:2615-1SUSE-SU-2022:2520-1SUSE-SU-2022:2177-1SUSE-SU-2022:2116-1
- kernel-rt openSUSE Leap Micro 5.2 5.3.18-150300.93.1
opensuse advisories openSUSE-SU-2022:2177-1
Is CVE-2022-21127 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-21127 updated cvss 5.6
hw: cpu: Incomplete cleanup in specific special register read operations (aka SRBDS update)
-
Red Hat Enterprise Linux 6 microcode_ctl Red Hat Enterprise Linux 7 microcode_ctl Red Hat Enterprise Linux 8 microcode_ctl Red Hat Enterprise Linux 9 microcode_ctlaffected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
5.51% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- n/a Intel(R) Processors
Classification
- Weakness
-
- CWE-459 Incomplete Cleanup
References
-
intel.com
/content/www/us/en/security-center/advisory/intel-sa-00615.html
patch, vendor-advisory
-
openwall.com
/lists/oss-security/2022/06/16/1
mailing-list, patch, third-party-advisory
-
debian.org
/security/2022/dsa-5178
vendor-advisory, third-party-advisory
-
security.netapp.com
/advisory/ntap-20220624-0008/
third-party-advisory
Sources
- CVE List CVE-2022-21127
- NVD CVE-2022-21127
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.