Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor

HighCVSS 8.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2090c1a2368339eab0e14dcde12fdf6a5ea6359d, 742a9b5ccd8c46caf983ca90c94f855466968e34, 83726330748981372bde86ed5411d7b306612991.

Low priority for now. Upgrade to Linux Linux 2090c1a2368339eab0e14dcde12fdf6a5ea6359d, 742a9b5ccd8c46caf983ca90c94f855466968e34, 83726330748981372bde86ed5411d7b306612991 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor ZCR_EL2 can be updated by a VHE guest hypervisor either using ZCR_EL2 (which traps) or ZCR_EL1 (which does not trap). KVM handles both in different way: - on ZCR_EL2 trap, ZCR_EL2.LEN is immediately capped at the VM's own VL limit. This has the potential to break existing SW that relies on the full LEN field to be stateful. - on ZCR_EL1 access, we do absolutely nothing. On restoring the SVE context for an L2 guest, we directly restore the guest hypervisor's view of ZCR_EL2 into the physical ZCR_EL2. If the guest's view of the register was updated using the ZCR_EL2 accessor, the value has already been sanitised (with the caveat mentioned above). But if the guest used ZCR_EL1, the raw value is written into the HW, and the L2 guest can now access VLs that it shouldn't. Fix all the above by moving the VL capping to the restore points, ensuring that: - the HW is always programmed with a capped value, irrespective of the accessor being used, - the ZCR_EL2.LEN field is always completely stateful, irrespective of the accessor being used. Additionally, move ZCR_EL2 to be a sanitised register, ensuring that only the LEN field is actually stateful. This requires some creative construction of the RES0 mask, as the sysreg generation script does not yet generate RAZ/WI fields. [maz: rewrote commit message, tidy up access_zcr_el2()]

Published
Jul 19, 2026
Updated
Oct 22, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-63941

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • b3d29a8230998b36afecf494b199211d26052785 and later · before 2090c1a2368339eab0e14dcde12fdf6a5ea6359daffected · git
    • b3d29a8230998b36afecf494b199211d26052785 and later · before 742a9b5ccd8c46caf983ca90c94f855466968e34affected · git
    • b3d29a8230998b36afecf494b199211d26052785 and later · before 83726330748981372bde86ed5411d7b306612991affected · git
    • before 6.11not affected · semver
    • 6.18.57 and later · up to and including 6.18.*not affected · semver
    • 7.0.12 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.11 and later · before 6.18.57
  • linux linux kernel6.19 and later · before 7.0.12
  • linux linux kernel7.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxfrom 0—
Debian:14linuxbefore 7.0.12-17.0.12-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-63939Jul 19, 2026 · KVM: SEV: Compute the correct max length of the in-GHCB scratch area
    37Monitor
  • ← EarlierCVE-2026-63940Jul 19, 2026 · KVM: SEV: Ignore Port I/O requests of length '0'
    37Monitor
  • Later →CVE-2026-63942Jul 19, 2026 · parport: Fix race between port and client registration
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2090c1a2368339eab0e14dcde12fdf6a5ea6359dVendor (CNA)
Linux Linux742a9b5ccd8c46caf983ca90c94f855466968e34Vendor (CNA)
Linux Linux83726330748981372bde86ed5411d7b306612991Vendor (CNA)
debian:linux7.0.12-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-638290 days apartnet: ip_gre: require CAP_NET_ADMIN in the device netns for changelink
    35Monitor
  • CVE-2026-639210 days apartip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().
    35Monitor
  • CVE-2026-640420 days apartvfio/pci: Check BAR resources before exporting a DMABUF
    35Monitor
  • CVE-2026-4617452 days apartx86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
    35Monitor
  • CVE-2026-31788116 days apartxen/privcmd: restrict usage in unprivileged domU
    32Monitor
  • CVE-2026-638330 days apartntfs3: reject direct userspace writes to reserved $LX* xattrs
    28Monitor

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

All records