LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46082: KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0 INVLPGA should cause a #UD when EFER.SVME is not set. Add a check to properly inject #UD when EFER.SVME=0. [sean: tag for stable@]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel KVM issue affecting AMD SVM virtualization behavior. A guest instruction should be rejected when SVM is disabled, but the kernel previously lacked that check. The public record does not provide CVSS, business impact, or exploit evidence, so urgency depends on whether affected KVM virtualization hosts are in use.

Executive priority

Treat this as a kernel virtualization hygiene update, not an emergency, unless your environment depends heavily on multi-tenant KVM on AMD hosts. Patch through normal kernel maintenance, with higher priority for shared virtualization infrastructure.

Technical view

KVM's SVM handling of INVLPGA did not inject an undefined-instruction exception when EFER.SVME was clear. The fix adds that check and is tagged for stable kernels. The CVE record lists Linux as affected across multiple kernel versions and references stable kernel commits, but does not describe privilege impact or exploitation prerequisites.

Likely exposure

Exposure is most plausible on Linux systems using KVM with AMD SVM virtualization. General Linux endpoints without KVM/SVM use are less likely to be relevant based on the description. Exact distro exposure requires checking vendor backports against the referenced stable commits.

Exploitation context

The source bundle says KEV is false and provides no cited evidence of active exploitation or public weaponization. It also does not describe a crash, escape, privilege escalation, or data exposure outcome, so exploitation significance remains unclear from the provided evidence.

Researcher notes

The available record documents a missing architectural exception check in KVM SVM. It does not provide CVSS, CWE, exploitability analysis, or downstream distro status. Avoid inferring impact beyond virtualization correctness until kernel or vendor advisories add detail.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable KVM SVM fix.
  • Prioritize hypervisors or hosts running KVM on AMD SVM-capable systems.
  • Check distribution advisories for backported fixes before relying only on version numbers.
  • Schedule reboot or live-patching according to standard kernel update procedures.

Validation and detection

  • Inventory Linux KVM hosts and identify AMD SVM virtualization usage.
  • Compare installed kernel builds against vendor advisories and referenced stable commits.
  • Confirm patched kernels are running after maintenance windows complete.
  • Track CVE, distro, and kernel stable updates for impact clarification.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5, ff092385e8285c03d8b148f42f46f98c5f4becd5unaffected
LinuxLinux2.6.32, 0, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.