# CVE-2024-25939: Denial of service in 3rd Generation Intel(R) Xeon(R) Scalable Processors

> A privileged local attacker can cause a denial of service on 3rd Generation Intel Xeon Scalable Processors due to mirrored region inconsistencies.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2024
- **Updated:** 19 Aug 2024
- **Also known as:** ALPINE-CVE-2024-25939, BELL-CVE-2024-25939, DEBIAN-CVE-2024-25939, GHSA-vrwq-6v5h-49vq, UBUNTU-CVE-2024-25939

## What is CVE-2024-25939?

CVE-2024-25939 is a medium-severity denial of service vulnerability in 3rd Generation Intel(R) Xeon(R) Scalable Processors, 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

Mirrored regions with different values in 3rd Generation Intel(R) Xeon(R) Scalable Processors may allow a privileged user to potentially enable denial of service via local access.

Weakness: CWE-1251 (Mirrored Regions with Different Values)

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


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

Apply the vendor's patch.

## Is CVE-2024-25939 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25939 is a medium-severity denial of service vulnerability in 3rd Generation Intel(R) Xeon(R) Scalable Processors, 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-2024-25939 in the wild and no public exploit code.

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

## Sources

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

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