Improper initialization of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information di
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.32% (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-microcode (Debian:12) 3.20220207.1; ucode-intel (openSUSE:Leap 15.3) 20220207-10.1; ucode-intel (openSUSE:Tumbleweed) 20220207-1.1.
Low priority for now. Upgrade to intel-microcode (Debian:12) 3.20220207.1; ucode-intel (openSUSE:Leap 15.3) 20220207-10.1; ucode-intel (openSUSE:Tumbleweed) 20220207-1.1 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
Improper initialization of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- Published
- Feb 9, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-665
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 6305 | cpe:2.3:h:intel:celeron_6305 |
| intel | celeron 6305e | cpe:2.3:h:intel:celeron_6305e |
| intel | celeron 6600he | cpe:2.3:h:intel:celeron_6600he |
| intel | core i3-1000g1 | cpe:2.3:h:intel:core_i3-1000g1 |
| intel | core i3-1000g4 | cpe:2.3:h:intel:core_i3-1000g4 |
| intel | core i3-1005g1 | cpe:2.3:h:intel:core_i3-1005g1 |
| intel | core i3-11100he | cpe:2.3:h:intel:core_i3-11100he |
| intel | core i3-1110g4 | cpe:2.3:h:intel:core_i3-1110g4 |
| intel | core i3-1115g4 | cpe:2.3:h:intel:core_i3-1115g4 |
| intel | core i3-1115g4e | cpe:2.3:h:intel:core_i3-1115g4e |
| intel | core i3-1115gre | cpe:2.3:h:intel:core_i3-1115gre |
| intel | core i3-1120g4 | cpe:2.3:h:intel:core_i3-1120g4 |
and 109 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel celeron 6305all versions
- intel celeron 6305eall versions
- intel celeron 6600heall versions
- intel core i3-1000g1all versions
- intel core i3-1000g4all versions
- intel core i3-1005g1all versions
- intel core i3-11100heall versions
- intel core i3-1110g4all versions
- intel core i3-1115g4all versions
- intel core i3-1115g4eall versions
- intel core i3-1115greall versions
- intel core i3-1120g4all versions
- intel core i3-1125g4all versions
- intel core i5-1030g4all versions
- intel core i5-1030g7all versions
- intel core i5-1035g1all versions
- intel core i5-1035g4all versions
- intel core i5-1035g7all versions
- intel core i5-11260hall versions
- intel core i5-11300hall 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 |
|---|---|---|---|
| Debian:12 | intel-microcode | before 3.20220207.1 | 3.20220207.1 |
| openSUSE:Leap 15.3 | ucode-intel | before 20220207-10.1 | 20220207-10.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20220207-1.1 | 20220207-1.1 |
| SUSE:HPE Helion OpenStack 8 | ucode-intel | before 20220207-13.93.1 | 20220207-13.93.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | ucode-intel | before 20220207-3.206.1 | 20220207-3.206.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | ucode-intel | before 20220207-3.70.1 | 20220207-3.70.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | ucode-intel | before 20220207-10.1 | 20220207-10.1 |
| SUSE:Linux Enterprise Server 12 SP5 | ucode-intel | before 20220207-3.38.1 | 20220207-3.38.1 |
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 |
|---|---|---|
| debian:intel-microcode | 3.20220207.1 · Debian:12 | Package registry (OSV) |
| opensuse:ucode-intel | 20220207-10.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:ucode-intel | 20220207-3.70.1 · SUSE:Linux Enterprise High Performance Computing 15-ESPOS | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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)
CWE-665 · Improper InitializationCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.