# CVE-2023-39368: Denial of service in Intel(R) Processors

> An unauthenticated attacker can cause a denial of service on systems using affected Intel processors via network access due to a bus lock regulator failure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** ALPINE-CVE-2023-39368, BELL-CVE-2023-39368, DEBIAN-CVE-2023-39368, GHSA-pvrq-gg3w-f695, UBUNTU-CVE-2023-39368

## What is CVE-2023-39368?

CVE-2023-39368 is a medium-severity denial of service vulnerability in Intel(R) Processors, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Protection mechanism failure of bus lock regulator for some Intel(R) Processors may allow an unauthenticated user to potentially enable denial of service via network access.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

Apply the vendor's patch.

## Is CVE-2023-39368 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39368 is a medium-severity denial of service vulnerability in Intel(R) Processors, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-39368 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-2023-39368/ (Markdown: https://insights.sbomify.com/CVE-2023-39368/index.md)
```

## Sources

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

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