# CVE-2022-0001: Information disclosure in Intel(R) Processors

> Authorized local users can exploit branch predictor sharing to disclose sensitive information from other contexts.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2022
- **Updated:** 5 May 2025
- **Also known as:** DEBIAN-CVE-2022-0001, UBUNTU-CVE-2022-0001, openSUSE-SU-2024:11930-1

## What is CVE-2022-0001?

CVE-2022-0001 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Binding Support Function, published on 11 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Non-transparent sharing of branch predictor selectors between contexts in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access.

## Which versions are affected by CVE-2022-0001?

It affects 458 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xen` | openSUSE:Tumbleweed | All versions | 4.16.0_06-3.1 |

Products: Intel Atom P5921b, Intel Atom P5931b, Intel Atom P5942b, Intel Atom P5962b, Intel Atom X6200fe, Intel Atom X6211e, Intel Atom X6212re, Intel Atom X6413e, Intel Atom X6425e, Intel Atom X6425re, Intel Atom X6427fe, Intel Celeron 5305u, Intel Celeron 6305, Intel Celeron 6305e, Intel Celeron 6600he, Intel Celeron G5205u, Intel Celeron G5305u, Intel Celeron G5900, Intel Celeron G5900t, Intel Celeron G5905 and 438 more.

## How do I fix CVE-2022-0001?

Apply the vendor's patch.

## Is CVE-2022-0001 being exploited?

There is no known exploitation of CVE-2022-0001 in the wild and no public exploit code.

Public exploit code:

- This script checks for Administrator privileges and then sets the necessary DWord values in the Windows registry to enable the hardware-level mitigation for CVE-2022-0001, as per Microsoft's guidance (github_poc): https://github.com/Sabecomoeh/CVE-2022-0001

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0001 and fix it if it is affected.

What it is: CVE-2022-0001 is a medium-severity vulnerability in Oracle Communications Cloud Native Core Binding Support Function, published on 11 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0001 in the wild and no public exploit code.

Affected product: Oracle Communications Cloud Native Core Binding Support Function. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0001/ (Markdown: https://insights.sbomify.com/CVE-2022-0001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0001
- OSV: https://osv.dev/vulnerability/CVE-2022-0001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0001/
Summaries are generated and may contain mistakes; the official description above is the record.