Review reviewHigh

CVE-2024-46830

Linux Linux, debian linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS Grab kvm->srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly leave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX reads guest memory. Note, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN via sync_regs(), which already holds SRCU. I.e. trying to precisely use kvm_vcpu_srcu_read_lock() around the problematic SMM code would cause problems. Acquiring SRCU isn't all that expensive, so for simplicity, grab it uncon...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.09.27
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS Grab kvm->srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly leave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX reads guest memory. Note, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN via sync_regs(), which already holds SRCU. I.e. trying to precisely use kvm_vcpu_srcu_read_lock() around the problematic SMM code would cause problems. Acquiring SRCU isn't all that expensive, so for simplicity, grab it uncon...

Affected product and versions

Product
Linux Linux, debian linux, linux kernel
Affected versions
>= e302786233e6bc512986d007c96458ccf5ca21c7 < 5f35099fa3d59caf10bda88b033538e90086684e, >= f7e570780efc5cec9b2ed1e0472a7da14e864fdb < fa297c33faefe51e10244e8a378837fca4963228, >= f7e570780efc5cec9b2ed1e0472a7da14e864fdb < 939375737b5a0b1bf9b1e75129054e11bc9ca65e, >= f7e570780efc5cec9b2ed1e0472a7da14e864fdb < ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9, >= f7e570780efc5cec9b2ed1e0472a7da14e864fdb < 4bcdd831d9d01e0fb64faea50732b59b2ee88da1, >= 080dbe7e9b86a0392d8dffc00d9971792afc121f, >= b4c0d89c92e957ecccce12e66b63875d0cc7af7e, >= 5.15.19 < 5.15.198, >= 5.10.97 < 5.11, >= 5.16.5 < 5.17, >= 5.17, 11.0, >= 5.17.1 < 6.1.110, >= 6.2 < 6.6.51, >= 6.7 < 6.10.10, 6.11
Fixed versions
5.11, 5.15.198, 5.17, 6.1.110, 6.6.51, 6.10.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, debian linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2024-46830 — Linux Linux, debian linux, linux kernel | SECUFOCUS NOW