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

KVM: x86: Unconditionally recompute CR8 intercept on PPR update

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 22 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.22% 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: Manual assessmentRemediation target: Manual assessment

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 22 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.

24 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 22 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian 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.

1 current
CVE-2026-64513 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-64513
238 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the "use TPR shadow" VM-execution control is 1 and the "virtualize APIC accesses" and "virtual-interrupt delivery" VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-48857

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

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 22 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: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the “use TPR shadow” VM-execution control is 1 and the “virtualize APIC accesses” and “virtual-interrupt delivery” VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).

What

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the “use TPR shadow” VM-execution control is 1 and the “virtualize APIC accesses” and “virtual-interrupt delivery” VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).

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 the affected interface may attempt exploitation when the stated preconditions are met. 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: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the “use TPR shadow” VM-execution control is 1 and the “virtualize APIC accesses” and “virtual-interrupt delivery” VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).

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 the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
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-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64509 https://www.cve.org/CVERecord?id=CVE-2026-64509 Référence CVE CVE-2026-64510 https://www.cve.org/CVERecord?id=CVE-2026-64510 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64516 https://www.cve.org/CVERecord?id=CVE-2026-64516 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64519 https://www.cve.org/CVERecord?id=CVE-2026-64519 Référence CVE CVE-2026-64520 https://www.cve.org/CVERecord?id=CVE-2026-64520 Référence CVE CVE-2026-64521 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-64497 Référence CVE CVE-2026-64499 https://www.cve.org/CVERecord?id=CVE-2026-64499 Référence CVE CVE-2026-64500 https://www.cve.org/CVERecord?id=CVE-2026-64500 Référence CVE CVE-2026-64503 https://www.cve.org/CVERecord?id=CVE-2026-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64519 https://www.cve.org/CVERecord?id=CVE-2026-64519 Référence CVE CVE-2026-64524 https://www.cve.org/CVERecord?id=CVE-2026-64524 Référence CVE CVE-2026-64525 https://www.cve.org/CVERecord?id=CVE-2026-64525 Référence CVE CVE-2026-64526 https://www.cve.org/CVERecord?id=CVE-2026-64526 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64411 Référence CVE CVE-2026-64412 https://www.cve.org/CVERecord?id=CVE-2026-64412 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64470 https://www.cve.org/CVERecord?id=CVE-2026-64470 Référence CVE CVE-2026-64471 https://www.cve.org/CVERecord?id=CVE-2026-64471 Référence CVE CVE-2026-64481 https://www.cve.org/CVERecord?id=CVE-2026-64481 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64541 https://www.cve.org/CVERecord?id=CVE-2026-64541 Référence CVE CVE-2026-64543 https://www.cve.org/CVERecord?id=CVE-2026-64543 Référence CVE CVE-2026-64544 https://www.cve.org/CVERecord?id=CVE-2026-64544 Référence CVE CVE-2026-64547 https://www.cve.org/CVERecord?id=CVE-2026-64547 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64553 https://www.cve.org/CVERecord?id=CVE-2026-64553 Référence CVE CVE-2026-64556 https://www.cve.org/CVERecord?id=CVE-2026-64556 Référence CVE CVE-2026-64561 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-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64509 https://www.cve.org/CVERecord?id=CVE-2026-64509 Référence CVE CVE-2026-64510 https://www.cve.org/CVERecord?id=CVE-2026-64510 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64516 https://www.cve.org/CVERecord?id=CVE-2026-64516 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64519 https://www.cve.org/CVERecord?id=CVE-2026-64519 Référence CVE CVE-2026-64520 https://www.cve.org/CVERecord?id=CVE-2026-64520 Référence CVE CVE-2026-64521 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-64495 Référence CVE CVE-2026-64496 https://www.cve.org/CVERecord?id=CVE-2026-64496 Référence CVE CVE-2026-64497 https://www.cve.org/CVERecord?id=CVE-2026-64497 Référence CVE CVE-2026-64500 https://www.cve.org/CVERecord?id=CVE-2026-64500 Référence CVE CVE-2026-64503 https://www.cve.org/CVERecord?id=CVE-2026-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64524 https://www.cve.org/CVERecord?id=CVE-2026-64524 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=CVE-2026-64527 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 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-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64509 https://www.cve.org/CVERecord?id=CVE-2026-64509 Référence CVE CVE-2026-64510 https://www.cve.org/CVERecord?id=CVE-2026-64510 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64523 https://www.cve.org/CVERecord?id=CVE-2026-64523 Référence CVE CVE-2026-64529 https://www.cve.org/CVERecord?id=CVE-2026-64529 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64534 https://www.cve.org/CVERecord?id=CVE-2026-64534 Référence CVE CVE-2026-64535 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-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64509 https://www.cve.org/CVERecord?id=CVE-2026-64509 Référence CVE CVE-2026-64510 https://www.cve.org/CVERecord?id=CVE-2026-64510 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64514 https://www.cve.org/CVERecord?id=CVE-2026-64514 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64516 https://www.cve.org/CVERecord?id=CVE-2026-64516 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64518 https://www.cve.org/CVERecord?id=CVE-2026-64518 Référence CVE CVE-2026-64519 https://www.cve.org/CVERecord?id=CVE-2026-64519 Référence CVE CVE-2026-64520 https://www.cve.org/CVERecord?id=CVE-2026-64520 Référence CVE CVE-2026-64521 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-64495 Référence CVE CVE-2026-64496 https://www.cve.org/CVERecord?id=CVE-2026-64496 Référence CVE CVE-2026-64497 https://www.cve.org/CVERecord?id=CVE-2026-64497 Référence CVE CVE-2026-64500 https://www.cve.org/CVERecord?id=CVE-2026-64500 Référence CVE CVE-2026-64503 https://www.cve.org/CVERecord?id=CVE-2026-64503 Référence CVE CVE-2026-64504 https://www.cve.org/CVERecord?id=CVE-2026-64504 Référence CVE CVE-2026-64505 https://www.cve.org/CVERecord?id=CVE-2026-64505 Référence CVE CVE-2026-64511 https://www.cve.org/CVERecord?id=CVE-2026-64511 Référence CVE CVE-2026-64512 https://www.cve.org/CVERecord?id=CVE-2026-64512 Référence CVE CVE-2026-64513 https://www.cve.org/CVERecord?id=CVE-2026-64513 Référence CVE CVE-2026-64515 https://www.cve.org/CVERecord?id=CVE-2026-64515 Référence CVE CVE-2026-64517 https://www.cve.org/CVERecord?id=CVE-2026-64517 Référence CVE CVE-2026-64524 https://www.cve.org/CVERecord?id=CVE-2026-64524 Référence CVE CVE-2026-64527 https://www.cve.org/CVERecord?id=CVE-2026-64527 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64536 https://www.cve.org/CVERecord?id=CVE-2026-64536 Référence CVE CVE-2026-64537 https://www.cve.org/CVERecord?id=CVE-2026-64537 Référence CVE CVE-2026-64538 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: < 4.11, 6.18.39 ≤ 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:57 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-48857
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CVSS base score, 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
    eb90f3417a0cc4880e979ccc84e41890d410ea5b < ff9c4c6428883182960cfe5c78928f0896d80ebc; eb90f3417a0cc4880e979ccc84e41890d410ea5b < 8c8e8ac22ee17d52f9eb2bc814bca7fab90fb8df; eb90f3417a0cc4880e979ccc84e41890d410ea5b < bb365a506b1e6fb050c0fceaad354fe395385ef0; 4.11 · Fixed: < 4.11; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    eb90f3417a0cc4880e979ccc84e41890d410ea5b < ff9c4c6428883182960cfe5c78928f0896d80ebc; eb90f3417a0cc4880e979ccc84e41890d410ea5b < 8c8e8ac22ee17d52f9eb2bc814bca7fab90fb8df; eb90f3417a0cc4880e979ccc84e41890d410ea5b < bb365a506b1e6fb050c0fceaad354fe395385ef0; 4.11 · Fixed: < 4.11; 6.18.39 ≤ 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-48857↗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-64513 · cve.blacktree.nl