dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-25743

HIGH · 7.1 CVSS v3.1 Published 2024-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability in Linux kernel through 6.9 allows an untrusted hypervisor to inject virtual interrupts 0 (Divide Error) and 14 (Page Fault) at arbitrary times into AMD SEV-SNP and SEV-ES protected virtual machines. This breaks the security isolation of SEV by enabling the hypervisor to deliberately trigger the SIGFPE signal handler in userspace applications running inside the encrypted VM.

MitigationApply kernel patches addressing SEV-ES/SEV-SNP interrupt handling when available. If running untrusted hypervisors is not required, consider using more trusted hypervisor solutions or ensure hypervisor integrity through measured boot and remote attestation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your Linux kernel version
    Run `uname -r` to get the running kernel version
    Affected if The kernel version is 6.9 or earlier (any version up to and including 6.9)
  2. Verify if AMD SEV/SEV-ES/SEV-SNP is enabled
    Check /sys/module/kvm_amd/parameters/sev or /sys/module/kvm_amd/parameters/sev_es; alternatively, run `dmesg | grep -i sev` and look for SEV, SEV-ES, or SEV-SNP initialization messages
    Affected if SEV-ES or SEV-SNP is listed as enabled or initialized in kernel messages
  3. Determine if the system is running as a virtual machine
    Run `virt-what` or check `dmidecode -s system-product-name` to identify if the system is a VM
    Affected if The system is a virtual machine running on a hypervisor
  4. Identify the hypervisor in use
    Check `/sys/hypervisor/type` or run `dmidecode | grep -i hypervisor` to determine which hypervisor hosts the VM
    Affected if The hypervisor is untrusted or not specifically designed for SEV-SNP/SEV-ES security

You are affected if you run Linux kernel 6.9 or earlier, have SEV-ES or SEV-SNP enabled, and operate on an untrusted hypervisor that could inject malicious interrupt vectors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply kernel patches addressing SEV-ES/SEV-SNP interrupt handling when available. If running untrusted hypervisors is not required, consider using more trusted hypervisor solutions or ensure hypervisor integrity through measured boot and remote attestation.

Recommended fix Moderate confidence

Linux kernel version newer than 6.9 (check with your distribution vendor for the specific patched version)

  1. Check your current Linux kernel version with: uname -r
  2. Determine your distribution vendor (Red Hat, SUSE, or other)
  3. For Red Hat systems: Run 'dnf check-update' or 'yum update' to fetch available kernel security updates
  4. For SUSE systems: Run 'zypper patch' or 'zypper update' to fetch available kernel security updates
  5. Apply the kernel update and reboot the system to load the patched kernel: systemctl reboot
  6. Verify the new kernel version is loaded after reboot with: uname -r
  7. Ensure AMD SEV-SNP and AMD SEV-ES features are re-enabled if they were temporarily disabled as a mitigation
Caveat Kernel updates may require system reboot and could have compatibility implications with custom kernel modules or specific hardware configurations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25743 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data