CVE-2024-39483: KVM: SVM: WARN on vNMI + NMI window iff NMIs are outright masked
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
Action score
22
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.4
- linux linux kernel6.6 and later · before 6.6.34
- linux linux kernel6.9 and later · before 6.9.5
- linux linux kernel6.10.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.40.1.el9_4 | 7.3.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-39480Jul 5, 2024 · kdb: Fix buffer overflow during tab-complete31Monitor
- ← EarlierCVE-2024-39481Jul 5, 2024 · media: mc: Fix graph walk in media_pipeline_start22Monitor
- Later →CVE-2024-39484Jul 5, 2024 · mmc: davinci: Don't strip remove function when driver is builtin22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1d87cf2eba46deaff6142366127f2323de9f84d1 | Vendor (CNA) |
| Linux Linux | b4bd556467477420ee3a91fbcba73c579669edc6 | Vendor (CNA) |
| Linux Linux | f79edaf7370986d73d204b36c50cc563a4c0f356 | Vendor (CNA) |
| azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 | 6.6.35.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 | - · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.0 | 5.15.162.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | 5.15.162.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 7.3.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.9.7-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package 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.
- TR-24-0883 · Jul 8, 2024(Linux Kernel Güncellemesi)
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.