CVE-2022-21151: Processor optimization removal or modification of security-critical code for some Intel(R) Processors may allow an authenticated user to pot
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: intel-ucode (Alpine:v3.13) 20220510-r0; intel-microcode (Debian:10) 3.20220510.1~deb10u1; intel-microcode (Debian:11) 3.20220510.1~deb11u1.
Low priority for now. Upgrade to intel-ucode (Alpine:v3.13) 20220510-r0; intel-microcode (Debian:10) 3.20220510.1~deb10u1; intel-microcode (Debian:11) 3.20220510.1~deb11u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Processor optimization removal or modification of security-critical code for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- Published
- May 12, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | celeron n6210 firmware | cpe:2.3:o:intel:celeron_n6210_firmware |
| intel | celeron n6210 | cpe:2.3:h:intel:celeron_n6210 |
| intel | celeron n4500 firmware | cpe:2.3:o:intel:celeron_n4500_firmware |
| intel | celeron n4500 | cpe:2.3:h:intel:celeron_n4500 |
| intel | celeron n4505 firmware | cpe:2.3:o:intel:celeron_n4505_firmware |
| intel | celeron n4505 | cpe:2.3:h:intel:celeron_n4505 |
| intel | celeron n5100 firmware | cpe:2.3:o:intel:celeron_n5100_firmware |
| intel | celeron n5100 | cpe:2.3:h:intel:celeron_n5100 |
| intel | celeron n5105 firmware | cpe:2.3:o:intel:celeron_n5105_firmware |
| intel | celeron n5105 | cpe:2.3:h:intel:celeron_n5105 |
| intel | celeron n6211 firmware | cpe:2.3:o:intel:celeron_n6211_firmware |
| intel | celeron n6211 | cpe:2.3:h:intel:celeron_n6211 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux11.0
- intel celeron j1750 firmwareall versions
- intel celeron j1800 firmwareall versions
- intel celeron j1850 firmwareall versions
- intel celeron j1900 firmwareall versions
- intel celeron j3060 firmwareall versions
- intel celeron j3160 firmwareall versions
- intel celeron j3355 firmwareall versions
- intel celeron j3355e firmwareall versions
- intel celeron j3455 firmwareall versions
- intel celeron j3455e firmwareall versions
- intel celeron j4005 firmwareall versions
- intel celeron j4025 firmwareall versions
- intel celeron j4105 firmwareall versions
- intel celeron j4125 firmwareall versions
- intel celeron j6412 firmwareall versions
- intel celeron j6413 firmwareall versions
- intel celeron n2805 firmwareall versions
- intel celeron n2806 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a Intel(R) Processors
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.13 | intel-ucode | before 20220510-r0 | 20220510-r0 |
| Debian:10 | intel-microcode | before 3.20220510.1~deb10u1 | 3.20220510.1~deb10u1 |
| Debian:11 | intel-microcode | before 3.20220510.1~deb11u1 | 3.20220510.1~deb11u1 |
| Debian:12 | intel-microcode | before 3.20220510.1 | 3.20220510.1 |
| openSUSE:Leap 15.3 | ucode-intel | before 20220510-150200.14.1 | 20220510-150200.14.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20220510-1.1 | 20220510-1.1 |
| Red Hat:enterprise_linux:9::baseos | microcode_ctl | before 4:20220809-1.el9 | 4:20220809-1.el9 |
| SUSE:HPE Helion OpenStack 8 | ucode-intel | before 20220510-13.97.1 | 20220510-13.97.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | ucode-intel | before 20220510-150100.3.210.1 | 20220510-150100.3.210.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | ucode-intel | before 20220510-150000.3.74.1 | 20220510-150000.3.74.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | ucode-intel | before 20220510-150200.14.1 | 20220510-150200.14.1 |
| SUSE:Linux Enterprise Server 12 SP5 | ucode-intel | before 20220510-3.42.2 | 20220510-3.42.2 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:intel-ucode | 20220510-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:intel-microcode | 3.20220510.1 · Debian:12 | Package registry (OSV) |
| opensuse:ucode-intel | 20220510-150200.14.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| red hat:microcode_ctl | 4:20220809-1.el9 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| suse:ucode-intel | 20220510-150200.14.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.