Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-39483: KVM: SVM: WARN on vNMI + NMI window iff NMIs are outright masked

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1d87cf2eba46deaff6142366127f2323de9f84d1, b4bd556467477420ee3a91fbcba73c579669edc6, f79edaf7370986d73d204b36c50cc563a4c0f356; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 -.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1d87cf2eba46deaff6142366127f2323de9f84d1, b4bd556467477420ee3a91fbcba73c579669edc6, f79edaf7370986d73d204b36c50cc563a4c0f356; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 - or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: WARN on vNMI + NMI window iff NMIs are outright masked When requesting an NMI window, WARN on vNMI support being enabled if and only if NMIs are actually masked, i.e. if the vCPU is already handling an NMI. KVM's ABI for NMIs that arrive simultanesouly (from KVM's point of view) is to inject one NMI and pend the other. When using vNMI, KVM pends the second NMI simply by setting V_NMI_PENDING, and lets the CPU do the rest (hardware automatically sets V_NMI_BLOCKING when an NMI is injected). However, if KVM can't immediately inject an NMI, e.g. because the vCPU is in an STI shadow or is running with GIF=0, then KVM will request an NMI window and trigger the WARN (but still function correctly). Whether or not the GIF=0 case makes sense is debatable, as the intent of KVM's behavior is to provide functionality that is as close to real hardware as possible. E.g. if two NMIs are sent in quick succession, the probability of both NMIs arriving in an STI shadow is infinitesimally low on real hardware, but significantly larger in a virtual environment, e.g. if the vCPU is preempted in the STI shadow. For GIF=0, the argument isn't as clear cut, because the window where two NMIs can collide is much larger in bare metal (though still small). That said, KVM should not have divergent behavior for the GIF=0 case based on whether or not vNMI support is enabled. And KVM has allowed simultaneous NMIs with GIF=0 for over a decade, since commit 7460fb4a3400 ("KVM: Fix simultaneous NMIs"). I.e. KVM's GIF=0 handling shouldn't be modified without a *really* good reason to do so, and if KVM's behavior were to be modified, it should be done irrespective of vNMI support.

Published
Jul 5, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.1
1.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-39483

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • fa4c027a7956f5e07697bfcb580d25eeb8471257 and later · before f79edaf7370986d73d204b36c50cc563a4c0f356affected · git
    • fa4c027a7956f5e07697bfcb580d25eeb8471257 and later · before 1d87cf2eba46deaff6142366127f2323de9f84d1affected · git
    • fa4c027a7956f5e07697bfcb580d25eeb8471257 and later · before b4bd556467477420ee3a91fbcba73c579669edc6affected · git
    • before 6.4not affected · semver
    • 6.6.34 and later · up to and including 6.6.*not affected · semver
    • 6.9.5 and later · up to and including 6.9.*not affected · semver
    • 6.10 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.40.1.el9_47.3.0-427.40.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-39480Jul 5, 2024 · kdb: Fix buffer overflow during tab-complete
    31Monitor
  • ← EarlierCVE-2024-39481Jul 5, 2024 · media: mc: Fix graph walk in media_pipeline_start
    22Monitor
  • Later →CVE-2024-39484Jul 5, 2024 · mmc: davinci: Don't strip remove function when driver is builtin
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1d87cf2eba46deaff6142366127f2323de9f84d1Vendor (CNA)
Linux Linuxb4bd556467477420ee3a91fbcba73c579669edc6Vendor (CNA)
Linux Linuxf79edaf7370986d73d204b36c50cc563a4c0f356Vendor (CNA)
azl3 kernel 6.6.22.1-2 on Azure Linux 3.06.6.35.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.0- · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.05.15.162.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.05.15.162.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.9.7-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records