Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-43133

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation

High7.9EPSS 0.13%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01. As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43133, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.9CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
redhat-SADPADP (enrichment)3.1High7.9CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
NVDNVD · Modified3.1High7.9CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.9.

Weakness

Affected products

  • Linux · Linux

    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < 10063e1251c1485034a018236080792ad083dcc5
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < c3b7015000988ba35ecd5648f4b2283960f00543
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < 3880e331b0b31d0d5d3702b124f6c93539cd478a
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < fce2fd4a2ca05670a91015aacccf96a1c26268fd
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < d464cf1ed900d47c85393d40b00017b6adfc2e6c
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < 0004ecb798b30e90d7ebfe74efae2d9423315a64
    • affected cc3ed80ae69f454c3d904af9f65394a540099723 – < 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References (15)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43133 badge
[![CVE-2026-43133](https://trackcve.app/badge/CVE-2026-43133.svg)](https://trackcve.app/cve/CVE-2026-43133)

Record last updated .