# CVE-2023-42667: Privilege escalation in Intel(R) Core(TM) Ultra Processor stream cache mechanism

> An authenticated local attacker can escalate privileges via improper isolation in the Intel Core Ultra Processor stream cache mechanism.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 14 Aug 2024
- **Updated:** 22 Aug 2024
- **Also known as:** ALPINE-CVE-2023-42667, BELL-CVE-2023-42667, DEBIAN-CVE-2023-42667, GHSA-fc9m-v759-xj58, UBUNTU-CVE-2023-42667

## What is CVE-2023-42667?

CVE-2023-42667 is a high-severity vulnerability in Intel(R) Core(TM) Ultra Processor stream cache mechanism, published on 14 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper isolation in the Intel(R) Core(TM) Ultra Processor stream cache mechanism may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC))

## Which versions are affected by CVE-2023-42667?


## How do I fix CVE-2023-42667?

Apply the vendor's patch.

## Is CVE-2023-42667 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42667 and fix it if it is affected.

What it is: CVE-2023-42667 is a high-severity vulnerability in Intel(R) Core(TM) Ultra Processor stream cache mechanism, published on 14 Aug 2024. 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-2023-42667 in the wild and no public exploit code.

Affected product: Intel(R) Core(TM) Ultra Processor stream cache mechanism. 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-2023-42667/ (Markdown: https://insights.sbomify.com/CVE-2023-42667/index.md)
```

## Sources

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

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