# CVE-2024-37020: Denial of service in Intel(R) Xeon(R) Processors

> An authenticated local user can cause a denial of service on Intel Xeon processors via specific instruction sequences.

- **Severity:** Medium 4.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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:** 12 Feb 2025
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2024-37020, BELL-CVE-2024-37020, DEBIAN-CVE-2024-37020, GHSA-5gqq-8pmr-37wh

## What is CVE-2024-37020?

CVE-2024-37020 is a medium-severity denial of service vulnerability in Intel(R) Xeon(R) Processors, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sequence of processor instructions leads to unexpected behavior in the Intel(R) DSA V1.0 for some Intel(R) Xeon(R) Processors may allow an authenticated user to potentially enable denial of service via local access.

Weakness: CWE-1281 (Sequence of Processor Instructions Leads to Unexpected Behavior)

## Which versions are affected by CVE-2024-37020?


## How do I fix CVE-2024-37020?

Apply the vendor's patch.

## Is CVE-2024-37020 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37020 and fix it if it is affected.

What it is: CVE-2024-37020 is a medium-severity denial of service vulnerability in Intel(R) Xeon(R) Processors, published on 12 Feb 2025. 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-2024-37020 in the wild and no public exploit code.

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

## Sources

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

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