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

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU

Linux · Linux

8.2HighCVSS 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 20 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 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 20 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.

25 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 20 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 · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 5 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 5 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 5 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 5 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 5 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-64287 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-64287
105 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it to stay within the number of implemented list registers. While this is generally the case, flush_hyp_vcpu() copies vgic_v3 verbatim and does not enforce this, so a value provided by the host is used at EL2 to index vgic_lr[] and access ICH_LR _EL2 (host -> EL2). Fix by clamping used_lrs to the number of implemented list registers after the copy, as the trusted path already does in vgic_flush_lr_state(). The number of implemented list registers is constant after init, so it is replicated once from kvm_vgic_global_state.nr_lr into hyp_gicv3_nr_lr rather than read on every entry.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64287 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU
70 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in the Kernel-based Virtual Machine (KVM) component of the Linux kernel on ARM64 systems. A highly privileged local attacker could exploit a vulnerability where the system fails to properly restrict memory access during a specific virtual machine operation. This could allow the attacker to read or write to sensitive memory areas, potentially leading to privilege escalation, where they gain unauthorized higher access, or cause a system crash (denial of service).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-48999

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 20 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: Bound used_lrs when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it to stay within the number of implemented list registers. While this is generally the case, flush_hyp_vcpu() copies vgic_v3 verbatim and does not enforce this, so a value provided by the host is used at EL2 to index vgic_lr[] and access ICH_LR<n>_EL2 (host -> EL2). Fix by clamping used_lrs to the number of implemented list registers after the copy, as the trusted path already does in vgic_flush_lr_state(). The number of implemented list registers is constant after init, so it is replicated once from kvm_vgic_global_state.nr_lr into hyp_gicv3_nr_lr rather than read on every entry.

What

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it to stay within the number of implemented list registers. While this is generally the case, flush_hyp_vcpu() copies vgic_v3 verbatim and does not enforce this, so a value provided by the host is used at EL2 to index vgic_lr[] and access ICH_LR<n>_EL2 (host -> EL2). Fix by clamping used_lrs to the number of implemented list registers after the copy, as the trusted path already does in vgic_flush_lr_state(). The number of implemented list registers is constant after init, so it is replicated once from kvm_vgic_global_state.nr_lr into hyp_gicv3_nr_lr rather than read on every entry.

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 elevated 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: Bound used_lrs when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it to stay within the number of implemented list registers. While this is generally the case, flush_hyp_vcpu() copies vgic_v3 verbatim and does not enforce this, so a value provided by the host is used at EL2 to index vgic_lr[] and access ICH_LR<n>_EL2 (host -> EL2). Fix by clamping used_lrs to the number of implemented list registers after the copy, as the trusted path already does in vgic_flush_lr_state(). The number of implemented list registers is constant after init, so it is replicated once from kvm_vgic_global_state.nr_lr into hyp_gicv3_nr_lr rather than read on every entry.

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 elevated 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
High: elevated access 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:H/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.PRHighPrivileges required: The attacker needs elevated or administrative 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-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 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-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64285 https://www.cve.org/CVERecord?id=CVE-2026-64285 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64288 https://www.cve.org/CVERecord?id=CVE-2026-64288 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64291 https://www.cve.org/CVERecord?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 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-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 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-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64285 https://www.cve.org/CVERecord?id=CVE-2026-64285 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64288 https://www.cve.org/CVERecord?id=CVE-2026-64288 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64291 https://www.cve.org/CVERecord?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64285 https://www.cve.org/CVERecord?id=CVE-2026-64285 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64288 https://www.cve.org/CVERecord?id=CVE-2026-64288 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64291 https://www.cve.org/CVERecord?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 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-64277 Référence CVE CVE-2026-64278 https://www.cve.org/CVERecord?id=CVE-2026-64278 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64282 https://www.cve.org/CVERecord?id=CVE-2026-64282 Référence CVE CVE-2026-64283 https://www.cve.org/CVERecord?id=CVE-2026-64283 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64285 https://www.cve.org/CVERecord?id=CVE-2026-64285 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64288 https://www.cve.org/CVERecord?id=CVE-2026-64288 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64291 https://www.cve.org/CVERecord?id=CVE-2026-64291 Référence CVE CVE-2026-64292 https://www.cve.org/CVERecord?id=CVE-2026-64292 Référence CVE CVE-2026-64293 https://www.cve.org/CVERecord?id=CVE-2026-64293 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64295 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64268 Référence CVE CVE-2026-64269 https://www.cve.org/CVERecord?id=CVE-2026-64269 Référence CVE CVE-2026-64271 https://www.cve.org/CVERecord?id=CVE-2026-64271 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=CVE-2026-64303 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64305 https://www.cve.org/CVERecord?id=CVE-2026-64305 Référence CVE CVE-2026-64306 https://www.cve.org/CVERecord?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64272 Référence CVE CVE-2026-64273 https://www.cve.org/CVERecord?id=CVE-2026-64273 Référence CVE CVE-2026-64274 https://www.cve.org/CVERecord?id=CVE-2026-64274 Référence CVE CVE-2026-64275 https://www.cve.org/CVERecord?id=CVE-2026-64275 Référence CVE CVE-2026-64276 https://www.cve.org/CVERecord?id=CVE-2026-64276 Référence CVE CVE-2026-64277 https://www.cve.org/CVERecord?id=CVE-2026-64277 Référence CVE CVE-2026-64279 https://www.cve.org/CVERecord?id=CVE-2026-64279 Référence CVE CVE-2026-64284 https://www.cve.org/CVERecord?id=CVE-2026-64284 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64289 https://www.cve.org/CVERecord?id=CVE-2026-64289 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64296 https://www.cve.org/CVERecord?id=CVE-2026-64296 Référence CVE CVE-2026-64297 https://www.cve.org/CVERecord?id=CVE-2026-64297 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64299 https://www.cve.org/CVERecord?id=CVE-2026-64299 Référence CVE CVE-2026-64301 https://www.cve.org/CVERecord?id=CVE-2026-64301 Référence CVE CVE-2026-64303 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45944 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=CVE-2026-64341 Référence CVE CVE-2026-64352 https://www.cve.org/CVERecord?id=CVE-2026-64352 Référence CVE CVE-2026-64361 https://www.cve.org/CVERecord?id=CVE-2026-64361 Référence CVE CVE-2026-64363 https://www.cve.org/CVERecord?id=CVE-2026-64363 Référence CVE CVE-2026-64364 https://www.cve.org/CVERecord?id=CVE-2026-64364 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028220LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：KVM: arm64: pKVMハイパーバイザのvCPUをフラッシュする際にused_lrsの範囲を制限する問題です。flush_hyp_vcpu()は、ホストのvGIC状態をハイパーバイザのプライベートvCPUに毎回の実行時にコピーします。vGICのリストレジスタのセーブおよびリストアはused_lrsをループの上限として使用し、実装されているリストレジスタの数内に留まることを想定しています。通常はその通りですが、flush_hyp_vcpu()はvgic_v3をそのままコピーし、この制限を課していません。そのため、ホストから提供された値がEL2でvgic_lr[]のインデックスに使われ、ICH_LR＜n＞_EL2にアクセスしてしまいます（ホスト -＞ EL2）。修正は、コピー後にused_lrsを実装されているリストレジスタの数に制限することで行われています。これは信頼パスがvgic_flush_lr_state()内で既に行っていることです。実装されているリストレジスタの数は初期化後は定数であるため、kvm_vgic_global_state.nr_lrからhyp_gicv3_nr_lrに一度だけ複製され、毎回のエントリで読み取られていません。

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.2, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
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 25 Jul 2026 · Last source change 17 Aug 2026, 04:52 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-48999
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 116 more · Fixed: kernel-64k-debug-debuginfo-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-matched-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debuginfo-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-matched-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-aarch64-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-ppc64le-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-s390x-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-x86_64-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.45.1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.45.1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.45.1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-687.45.1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 273 more
    After
    bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; kernel-modules as a component of Red Hat Enterprise Linux 8; kernel-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt as a component of Red Hat Enterprise Linux 8; kernel-rt-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-kvm as a component of Red Hat Enterprise Linux 8; and 40 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    be66e67f175096f283c9d5614c4991fc9e7ed975 < 2c5e72b9fbf83fdfa724e9f1af0f418ccf8739b8; be66e67f175096f283c9d5614c4991fc9e7ed975 < 9fa301d8298778dd799fa4dcf7a7f440715d146e; be66e67f175096f283c9d5614c4991fc9e7ed975 < c646431865f4b1a5b14067233fa27b11e05e0d46; be66e67f175096f283c9d5614c4991fc9e7ed975 < 7fca3fcef81c713bc82a37bf741e0f28e6d04a6f; be66e67f175096f283c9d5614c4991fc9e7ed975 < 8cc8bbbfab14c22c5551d0dd19b208a44b141c76; 6.2 · Fixed: < 6.2; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    be66e67f175096f283c9d5614c4991fc9e7ed975 < 2c5e72b9fbf83fdfa724e9f1af0f418ccf8739b8; be66e67f175096f283c9d5614c4991fc9e7ed975 < 9fa301d8298778dd799fa4dcf7a7f440715d146e; be66e67f175096f283c9d5614c4991fc9e7ed975 < c646431865f4b1a5b14067233fa27b11e05e0d46; be66e67f175096f283c9d5614c4991fc9e7ed975 < 7fca3fcef81c713bc82a37bf741e0f28e6d04a6f; be66e67f175096f283c9d5614c4991fc9e7ed975 < 8cc8bbbfab14c22c5551d0dd19b208a44b141c76; 6.2 · Fixed: < 6.2; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-48999↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-64287 · cve.blacktree.nl