Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64286KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vCPU context into the hyp's private vCPU on every run. ctxt_to_vcpu() expects a guest context to have a NULL __hyp_running_vcpu, which is only ever set on the host context, so that it resolves the vCPU via container_of(). While this is generally the case, flush_hyp_vcpu() copies the context verbatim and does not enforce this, so a value provided by the host is dereferenced at EL2 (host -> EL2). Fix by clearing __hyp_running_vcpu after the copy.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 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-64286, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Modified3.1High8.2CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected be66e67f175096f283c9d5614c4991fc9e7ed975 – < 477145860dba4c30f0b4e36f02f4c5291c1c888b
    • affected be66e67f175096f283c9d5614c4991fc9e7ed975 – < dfaef40d8a1533940fc1af788d70fce07362b4ce
    • affected be66e67f175096f283c9d5614c4991fc9e7ed975 – < 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa
    • affected be66e67f175096f283c9d5614c4991fc9e7ed975 – < d4f4d61715d1061ba83b88196a3605662be30750
    • affected be66e67f175096f283c9d5614c4991fc9e7ed975 – < e8042f6e1d7befb2fb6b10a75918642bcd0acf9a
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .