BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-63941High confidence

KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 14 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-63941 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-63941
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
Summary
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()]
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-63941 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) for arm64 architecture. This vulnerability allows a guest hypervisor with Virtualization Host Extensions (VHE) to bypass intended security controls. By manipulating the SVE Control Register (ZCR_EL2) through an untrapped access, a nested guest (L2 guest) can gain unauthorized access to Vector Lengths (VLs), potentially leading to information disclosure.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45714

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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()]

What

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()]

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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()]

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-63917 Référence CVE CVE-2026-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-63922 https://www.cve.org/CVERecord?id=CVE-2026-63922 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 Référence CVE CVE-2026-63925 https://www.cve.org/CVERecord?id=CVE-2026-63925 Référence CVE CVE-2026-63926 https://www.cve.org/CVERecord?id=CVE-2026-63926 Référence CVE CVE-2026-63928 https://www.cve.org/CVERecord?id=CVE-2026-63928 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63969 https://www.cve.org/CVERecord?id=CVE-2026-63969 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63985 https://www.cve.org/CVERecord?id=CVE-2026-63985 Référence CVE CVE-2026-63986 https://www.cve.org/CVERecord?id=CVE-2026-63986 Référence CVE CVE-2026-63987 https://www.cve.org/CVERecord?id=CVE-2026-63987 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63932 Référence CVE CVE-2026-63933 https://www.cve.org/CVERecord?id=CVE-2026-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63935 https://www.cve.org/CVERecord?id=CVE-2026-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.11, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 5 Aug 2026, 12:37 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45714
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD awaiting enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-base-6.12.0-160000.38.1.160000.2.24 as component of SUSE Linux Enterprise Server 16.0; kernel-default-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-livepatch-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-html-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-macros-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-obs-qa-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-syms-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-zfcpdump-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; cluster-md-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; dlm-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; gfs2-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; and 38 more
    After
    SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45714↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-63941 · cve.blacktree.nl