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

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async

Linux · Linux

7.0HighCVSS 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 34 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.14% 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 34 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 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.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 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-64219 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-64219
151 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 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64219 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async
50 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)
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-48627

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 34 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: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)

What

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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 → Uncontrolled Recursion → 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
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-674 ↗

CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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:H/PR:L/UI:N/S:U/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's 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.
CWE-674
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
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-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-63884 Référence CVE CVE-2026-63886 https://www.cve.org/CVERecord?id=CVE-2026-63886 Référence CVE CVE-2026-63887 https://www.cve.org/CVERecord?id=CVE-2026-63887 Référence CVE CVE-2026-63888 https://www.cve.org/CVERecord?id=CVE-2026-63888 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-64018 https://www.cve.org/CVERecord?id=CVE-2026-64018 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 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-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64496 https://www.cve.org/CVERecord?id=CVE-2026-64496 Référence CVE CVE-2026-64641 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-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64243 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-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 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-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64243 https://www.cve.org/CVERecord?id=CVE-2026-64243 Référence CVE CVE-2026-64244 https://www.cve.org/CVERecord?id=CVE-2026-64244 Référence CVE CVE-2026-64245 https://www.cve.org/CVERecord?id=CVE-2026-64245 Référence CVE CVE-2026-64246 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-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64244 https://www.cve.org/CVERecord?id=CVE-2026-64244 Référence CVE CVE-2026-64245 https://www.cve.org/CVERecord?id=CVE-2026-64245 Référence CVE CVE-2026-64246 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-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 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-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64243 https://www.cve.org/CVERecord?id=CVE-2026-64243 Référence CVE CVE-2026-64244 https://www.cve.org/CVERecord?id=CVE-2026-64244 Référence CVE CVE-2026-64245 https://www.cve.org/CVERecord?id=CVE-2026-64245 Référence CVE CVE-2026-64246 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Référence CVE CVE-2026-64587 https://www.cve.org/CVERecord?id=CVE-2026-64587 Gestion détaillée du document le 28 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la

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

d?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53136 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-63879 https://www.cve.org/CVERecord?id=CVE-2026-63879 Référence CVE CVE-2026-63884 https://www.cve.org/CVERecord?id=CVE-2026-63884 Référence CVE CVE-2026-63887 https://www.cve.org/CVERecord?id=CVE-2026-63887 Référence CVE CVE-2026-63888 https://www.cve.org/CVERecord?id=CVE-2026-63888 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Gestion détaillée du document le 21 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Gestion détaillée du document le 07 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=CVE-2026-64212 Référence CVE CVE-2026-64213 https://www.cve.org/CVERecord?id=CVE-2026-64213 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64215 https://www.cve.org/CVERecord?id=CVE-2026-64215 Référence CVE CVE-2026-64216 https://www.cve.org/CVERecord?id=CVE-2026-64216 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027854LinuxのLinux Kernelにおける再帰制御に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：drm/amd/display: dc_process_dmub_aux_transfer_async内のペイロード長およびlink_indexの検証。 【原因と対策】dc_process_dmub_aux_transfer_async()は16バイトのスタックバッファ（dpaux.data[16]）にpayload-＞lengthバイトをコピーしますが、これはASSERT()でのみ保護されており、リリースビルドでは無効です。もし呼び出し元がlength ＞ 16を渡した場合、memcpyによるスタックバッファオーバーフローが発生します。加えて、link_indexはdc-＞links[]の参照に用いられますが、dc-＞link_countとの境界チェックがないため、範囲外アクセスのリスクがあります。ASSERT()をpayload-＞lengthが宛先バッファサイズを超えた場合にfalseを返す厳格な実行時チェックに置き換え、link_indexが使用される前に境界チェックを追加しました。（コミットba4caa9fecdf7a38f98c878ad05a8a64148b6881からチェリーピックされています）

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: < 5.13, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 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 24 Jul 2026 · Last source change 5 Aug 2026, 12:40 UTC · CWE-674 · Uncontrolled Recursion

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-48627
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

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 182 more · Fixed: bpftool-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.156.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.156.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.156.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.156.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.156.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.156.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    After
    bpftool as a component of Red Hat Enterprise Linux 7; kernel as a component of Red Hat Enterprise Linux 7; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7; kernel-bootwrapper as a component of Red Hat Enterprise Linux 7; kernel-debug as a component of Red Hat Enterprise Linux 7; kernel-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-devel as a component of Red Hat Enterprise Linux 7; kernel-doc as a component of Red Hat Enterprise Linux 7; kernel-headers as a component of Red Hat Enterprise Linux 7; kernel-kdump as a component of Red Hat Enterprise Linux 7; kernel-kdump-devel as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-doc as a component of Red Hat Enterprise Linux 7; kernel-rt-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-trace as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt.src as a component of Red Hat Enterprise Linux 7; kernel-tools as a component of Red Hat Enterprise Linux 7; kernel-tools-libs as a component of Red Hat Enterprise Linux 7; kernel-tools-libs-devel as a component of Red Hat Enterprise Linux 7; kernel.src as a component of Red Hat Enterprise Linux 7; perf as a component of Red Hat Enterprise Linux 7; python-perf as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; and 20 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.49.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.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.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.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.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.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.49.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.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 732 more
    Red Hat Product Security ↗
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-48627↗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-64219 · cve.blacktree.nl