# CVE-2024-25743: Other in n/a

> A malicious hypervisor can inject virtual interrupts to trigger SIGFPE in userspace, causing denial of service on AMD SEV systems.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 15 May 2024
- **Updated:** 14 Mar 2025
- **Also known as:** DEBIAN-CVE-2024-25743, GHSA-m82c-2r7m-qgcj, ROOT-OS-DEBIAN-11-CVE-2024-25743, ROOT-OS-DEBIAN-12-CVE-2024-25743, ROOT-OS-UBUNTU-2204-CVE-2024-25743, UBUNTU-CVE-2024-25743

## What is CVE-2024-25743?

CVE-2024-25743 is a high-severity vulnerability in n/a, published on 15 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 through 6.9, an untrusted hypervisor can inject virtual interrupts 0 and 14 at any point in time and can trigger the SIGFPE signal handler in userspace applications. This affects AMD SEV-SNP and AMD SEV-ES.

Weakness: CWE-20 (Improper Input Validation)

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


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

Apply the vendor's patch.

## Is CVE-2024-25743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25743 is a high-severity vulnerability in n/a, published on 15 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-25743 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-25743/ (Markdown: https://insights.sbomify.com/CVE-2024-25743/index.md)
```

## Sources

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

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