# CVE-2022-44611: Privilege escalation in Intel(R) Processors

> A privileged user with adjacent access can escalate privileges due to improper input validation in Intel processor BIOS firmware.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-rrf8-fw37-jc8w

## What is CVE-2022-44611?

CVE-2022-44611 is a medium-severity vulnerability in Intel(R) Processors, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 298 products.


Products: Intel Atom X6200fe Firmware, Intel Atom X6211e Firmware, Intel Atom X6212re Firmware, Intel Atom X6413e Firmware, Intel Atom X6414re Firmware, Intel Atom X6425e Firmware, Intel Atom X6425re Firmware, Intel Atom X6427fe Firmware, Intel Celeron J6413 Firmware, Intel Celeron N6211 Firmware, Intel Core I3-1000g1 Firmware, Intel Core I3-1000g4 Firmware, Intel Core I3-1005g1 Firmware, Intel Core I3-10100 Firmware, Intel Core I3-10100e Firmware, Intel Core I3-10100f Firmware, Intel Core I3-10100t Firmware, Intel Core I3-10100te Firmware, Intel Core I3-10100y Firmware, Intel Core I3-10105 Firmware and 278 more.

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

No fix has been published for CVE-2022-44611 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-44611 being exploited?

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

## Other vulnerabilities in Intel(R) Processors

- [CVE-2023-25756](https://insights.sbomify.com/CVE-2023-25756/): Memory corruption in Intel(R) Processors (medium 4.6)
- [CVE-2023-22329](https://insights.sbomify.com/CVE-2023-22329/): Denial of service in Intel(R) Processors (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44611 is a medium-severity vulnerability in Intel(R) Processors, published on 11 Aug 2023. 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-44611 in the wild and no public exploit code.

Affected product: Intel(R) Processors. 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-44611/ (Markdown: https://insights.sbomify.com/CVE-2022-44611/index.md)
```

## Sources

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

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