# CVE-2024-21853: Denial of service in 4th and 5th Generation Intel(R) Xeon(R) Processors

> An authorized local user can cause a denial of service on Intel Xeon processors due to improper finite state machines in hardware logic.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/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:** 13 Nov 2024
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2024-21853, BELL-CVE-2024-21853, DEBIAN-CVE-2024-21853, GHSA-f58g-ghv3-pqv3, UBUNTU-CVE-2024-21853

## What is CVE-2024-21853?

CVE-2024-21853 is a medium-severity denial of service vulnerability in 4th and 5th Generation Intel(R) Xeon(R) Processors, published on 13 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper finite state machines (FSMs) in the hardware logic in some 4th and 5th Generation Intel(R) Xeon(R) Processors may allow an authorized user to potentially enable denial of service via local access.

Weakness: CWE-1245 (Improper Finite State Machines (FSMs) in Hardware Logic)

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


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

Apply the vendor's patch.

## Is CVE-2024-21853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21853 is a medium-severity denial of service vulnerability in 4th and 5th Generation Intel(R) Xeon(R) Processors, published on 13 Nov 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-2024-21853 in the wild and no public exploit code.

Affected product: 4th and 5th Generation 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-21853/ (Markdown: https://insights.sbomify.com/CVE-2024-21853/index.md)
```

## Sources

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

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