# CVE-2024-25742: Denial of service in n/a

> An untrusted hypervisor can inject virtual interrupts to trigger handlers, causing denial of service in AMD SEV-SNP/ES environments.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 17 May 2024
- **Updated:** 27 Mar 2025
- **Also known as:** DEBIAN-CVE-2024-25742, ROOT-OS-DEBIAN-11-CVE-2024-25742, ROOT-OS-DEBIAN-12-CVE-2024-25742, UBUNTU-CVE-2024-25742

## What is CVE-2024-25742?

CVE-2024-25742 is a medium-severity denial of service vulnerability in n/a, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel before 6.9, an untrusted hypervisor can inject virtual interrupt 29 (#VC) at any point in time and can trigger its handler. This affects AMD SEV-SNP and AMD SEV-ES.

Weakness: CWE-828 (Signal Handler with Functionality that is not Asynchronous-Safe)

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


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

Upgrade to a fixed version.

## Is CVE-2024-25742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25742 is a medium-severity denial of service vulnerability in n/a, published on 17 May 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-25742 in the wild and no public exploit code.

Affected product: n/a. 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-25742/ (Markdown: https://insights.sbomify.com/CVE-2024-25742/index.md)
```

## Sources

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

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