CVE-2024-39483 Details
Description
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.
A vulnerability in the Linux kernel's KVM (Kernel-based Virtual Machine) module for AMD processors (SVM) has been addressed. The issue arises when virtual Non-Maskable Interrupts (vNMIs) are enabled and the vCPU is already handling an NMI, creating a conflict in NMI management. KVM's approach to simultaneous NMIs is to inject one and pend the other. However, if an NMI cannot be immediately injected due to the vCPU's state, KVM will request an NMI window, which can lead to incorrect handling when vNMI support is active. This vulnerability affects the Linux kernel stable tree.
Users can update to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Sep 10, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1d87cf2eba46deaff6142366127f2323de9f84d1 | kernel.org | Mailing ListPatch |
| https://git.kernel.org/stable/c/b4bd556467477420ee3a91fbcba73c579669edc6 | kernel.org | Mailing ListPatch |
| https://git.kernel.org/stable/c/f79edaf7370986d73d204b36c50cc563a4c0f356 | kernel.org | Mailing ListPatch |
| https://git.kernel.org/stable/c/1d87cf2eba46deaff6142366127f2323de9f84d1 | CVE | Mailing ListPatch |
| https://git.kernel.org/stable/c/b4bd556467477420ee3a91fbcba73c579669edc6 | CVE | Mailing ListPatch |
| https://git.kernel.org/stable/c/f79edaf7370986d73d204b36c50cc563a4c0f356 | CVE | Mailing ListPatch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 6.4 >= 6.6, < 6.6.34 >= 6.9, < 6.9.5 6.10.0 rc1 6.10.0 rc2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 21, 2024 | CVE Modified | CVE |
| Jul 8, 2024 | Initial Analysis | [email protected] |
| Jul 5, 2024 | New CVE Received | kernel.org |