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

hwrng: virtio: clamp device-reported used.len at copy_data()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% 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: Within 30 daysRemediation target: Within 180 days

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.96-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-64456 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-64456
283 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio: clamp device-reported used.len at copy_data() random_recv_done() stores the device-reported used.len directly into vi->data_avail. copy_data() then indexes vi->data[] using vi->data_idx (advanced by previous copy_data() calls) and issues a memcpy() without re-validating either value against the posted buffer size sizeof(vi->data) (SMP_CACHE_BYTES bytes, typically 32 or 64). A malicious or buggy virtio-rng backend can set used.len beyond sizeof(vi->data), steering the memcpy() past the end of the inline array into adjacent kmalloc-1k slab bytes. hwrng_fillfn() mixes those bytes into the guest RNG, and guest root can also observe them directly via /dev/hwrng. Concrete impact is inside the guest: - Memory-safety / hardening: any virtio-rng backend that over-reports used.len causes the driver to read past vi->data into unrelated slab contents. hwrng_fillfn() is a kernel thread that runs as soon as the device is probed; no guest userspace interaction is required to first-trigger the OOB. - Cross-boundary leak (confidential-compute threat model): a malicious hypervisor cooperating with a malicious or compromised guest root userspace can use /dev/hwrng as a leak channel for guest-kernel heap data. The host sets a large used.len, guest root reads /dev/hwrng, and the returned bytes contain guest kernel slab contents that were adjacent to vi->data. In practice, confidential-compute guests (SEV-SNP, TDX) usually disable virtio-rng entirely, so this path is narrow, but the fix is still worth carrying because the underlying memory-safety bug contaminates the guest RNG on any host. KASAN confirms the OOB on a 7.1-rc4 guest whose virtio-rng backend has been patched to report used.len = 0x10000: BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0 Read of size 64 at addr ffff88800ae0ba20 by task hwrng/52 Call Trace: __asan_memcpy+0x23/0x60 virtio_read+0x394/0x5d0 hwrng_fillfn+0xb2/0x470 kthread+0x2cc/0x3a0 Allocated by task 1: probe_common+0xa5/0x660 virtio_dev_probe+0x549/0xbc0 The buggy address belongs to the object at ffff88800ae0b800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 0 bytes to the right of allocated 544-byte region [ffff88800ae0b800, ffff88800ae0ba20) Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer overflow in USB transport layer"), which hardened usb9pfs_rx_complete() against unchecked device-reported length in the USB 9p transport. With the clamp at point of use and array_index_nospec() in place, the same harness boots cleanly: copy_data() returns zero for the bogus report, the device-supplied bytes after data_idx are discarded, and the driver issues a fresh request.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64456 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: hwrng: virtio: clamp device-reported used.len at copy_data()
43 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's virtio-rng driver. A malicious or buggy virtualized hardware random number generator (virtio-rng) backend can report an overly large data length to the guest operating system. This unchecked length can lead to an out-of-bounds read, causing the driver to access memory beyond its intended buffer. This vulnerability can result in information disclosure, where sensitive guest-kernel heap data may be leaked to a malicious hypervisor or a compromised guest root user.
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-48800

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio: clamp device-reported used.len at copy_data() random_recv_done() stores the device-reported used.len directly into vi->data_avail. copy_data() then indexes vi->data[] using vi->data_idx (advanced by previous copy_data() calls) and issues a memcpy() without re-validating either value against the posted buffer size sizeof(vi->data) (SMP_CACHE_BYTES bytes, typically 32 or 64). A malicious or buggy virtio-rng backend can set used.len beyond sizeof(vi->data), steering the memcpy() past the end of the inline array into adjacent kmalloc-1k slab bytes. hwrng_fillfn() mixes those bytes into the guest RNG, and guest root can also observe them directly via /dev/hwrng. Concrete impact is inside the guest: - Memory-safety / hardening: any virtio-rng backend that over-reports used.len causes the driver to read past vi->data into unrelated slab contents. hwrng_fillfn() is a kernel thread that runs as soon as the device is probed; no guest userspace interaction is required to first-trigger the OOB. - Cross-boundary leak (confidential-compute threat model): a malicious hypervisor cooperating with a malicious or compromised guest root userspace can use /dev/hwrng as a leak channel for guest-kernel heap data. The host sets a large used.len, guest root reads /dev/hwrng, and the returned bytes contain guest kernel slab contents that were adjacent to vi->data. In practice, confidential-compute guests (SEV-SNP, TDX) usually disable virtio-rng entirely, so this path is narrow, but the fix is still worth carrying because the underlying memory-safety bug contaminates the guest RNG on any host. KASAN confirms the OOB on a 7.1-rc4 guest whose virtio-rng backend has been patched to report used.len = 0x10000: BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0 Read of size 64 at addr ffff88800ae0ba20 by task hwrng/52 Call Trace: __asan_memcpy+0x23/0x60 virtio_read+0x394/0x5d0 hwrng_fillfn+0xb2/0x470 kthread+0x2cc/0x3a0 Allocated by task 1: probe_common+0xa5/0x660 virtio_dev_probe+0x549/0xbc0 The buggy address belongs to the object at ffff88800ae0b800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 0 bytes to the right of allocated 544-byte region [ffff88800ae0b800, ffff88800ae0ba20) Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer overflow in USB transport layer"), which hardened usb9pfs_rx_complete() against unchecked device-reported length in the USB 9p transport. With the clamp at point of use and array_index_nospec() in place, the same harness boots cleanly: copy_data() returns zero for the bogus report, the device-supplied bytes after data_idx are discarded, and the driver issues a fresh request.

What

In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio: clamp device-reported used.len at copy_data() random_recv_done() stores the device-reported used.len directly into vi->data_avail. copy_data() then indexes vi->data[] using vi->data_idx (advanced by previous copy_data() calls) and issues a memcpy() without re-validating either value against the posted buffer size sizeof(vi->data) (SMP_CACHE_BYTES bytes, typically 32 or 64). A malicious or buggy virtio-rng backend can set used.len beyond sizeof(vi->data), steering the memcpy() past the end of the inline array into adjacent kmalloc-1k slab bytes. hwrng_fillfn() mixes those bytes into the guest RNG, and guest root can also observe them directly via /dev/hwrng. Concrete impact is inside the guest: - Memory-safety / hardening: any virtio-rng backend that over-reports used.len causes the driver to read past vi->data into unrelated slab contents. hwrng_fillfn() is a kernel thread that runs as soon as the device is probed; no guest userspace interaction is required to first-trigger the OOB. - Cross-boundary leak (confidential-compute threat model): a malicious hypervisor cooperating with a malicious or compromised guest root userspace can use /dev/hwrng as a leak channel for guest-kernel heap data. The host sets a large used.len, guest root reads /dev/hwrng, and the returned bytes contain guest kernel slab contents that were adjacent to vi->data. In practice, confidential-compute guests (SEV-SNP, TDX) usually disable virtio-rng entirely, so this path is narrow, but the fix is still worth carrying because the underlying memory-safety bug contaminates the guest RNG on any host. KASAN confirms the OOB on a 7.1-rc4 guest whose virtio-rng backend has been patched to report used.len = 0x10000: BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0 Read of size 64 at addr ffff88800ae0ba20 by task hwrng/52 Call Trace: __asan_memcpy+0x23/0x60 virtio_read+0x394/0x5d0 hwrng_fillfn+0xb2/0x470 kthread+0x2cc/0x3a0 Allocated by task 1: probe_common+0xa5/0x660 virtio_dev_probe+0x549/0xbc0 The buggy address belongs to the object at ffff88800ae0b800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 0 bytes to the right of allocated 544-byte region [ffff88800ae0b800, ffff88800ae0ba20) Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer overflow in USB transport layer"), which hardened usb9pfs_rx_complete() against unchecked device-reported length in the USB 9p transport. With the clamp at point of use and array_index_nospec() in place, the same harness boots cleanly: copy_data() returns zero for the bogus report, the device-supplied bytes after data_idx are discarded, and the driver issues a fresh request.

Why

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

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. 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: hwrng: virtio: clamp device-reported used.len at copy_data() random_recv_done() stores the device-reported used.len directly into vi->data_avail. copy_data() then indexes vi->data[] using vi->data_idx (advanced by previous copy_data() calls) and issues a memcpy() without re-validating either value against the posted buffer size sizeof(vi->data) (SMP_CACHE_BYTES bytes, typically 32 or 64). A malicious or buggy virtio-rng backend can set used.len beyond sizeof(vi->data), steering the memcpy() past the end of the inline array into adjacent kmalloc-1k slab bytes. hwrng_fillfn() mixes those bytes into the guest RNG, and guest root can also observe them directly via /dev/hwrng. Concrete impact is inside the guest: - Memory-safety / hardening: any virtio-rng backend that over-reports used.len causes the driver to read past vi->data into unrelated slab contents. hwrng_fillfn() is a kernel thread that runs as soon as the device is probed; no guest userspace interaction is required to first-trigger the OOB. - Cross-boundary leak (confidential-compute threat model): a malicious hypervisor cooperating with a malicious or compromised guest root userspace can use /dev/hwrng as a leak channel for guest-kernel heap data. The host sets a large used.len, guest root reads /dev/hwrng, and the returned bytes contain guest kernel slab contents that were adjacent to vi->data. In practice, confidential-compute guests (SEV-SNP, TDX) usually disable virtio-rng entirely, so this path is narrow, but the fix is still worth carrying because the underlying memory-safety bug contaminates the guest RNG on any host. KASAN confirms the OOB on a 7.1-rc4 guest whose virtio-rng backend has been patched to report used.len = 0x10000: BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0 Read of size 64 at addr ffff88800ae0ba20 by task hwrng/52 Call Trace: __asan_memcpy+0x23/0x60 virtio_read+0x394/0x5d0 hwrng_fillfn+0xb2/0x470 kthread+0x2cc/0x3a0 Allocated by task 1: probe_common+0xa5/0x660 virtio_dev_probe+0x549/0xbc0 The buggy address belongs to the object at ffff88800ae0b800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 0 bytes to the right of allocated 544-byte region [ffff88800ae0b800, ffff88800ae0ba20) Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer overflow in USB transport layer"), which hardened usb9pfs_rx_complete() against unchecked device-reported length in the USB 9p transport. With the clamp at point of use and array_index_nospec() in place, the same harness boots cleanly: copy_data() returns zero for the bogus report, the device-supplied bytes after data_idx are discarded, and the driver issues a fresh request.

Why

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

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.INoneIntegrity impact: No direct loss is represented by this metric.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.
Unauthenticated
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-64447 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64451 https://www.cve.org/CVERecord?id=CVE-2026-64451 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64453 https://www.cve.org/CVERecord?id=CVE-2026-64453 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64457 https://www.cve.org/CVERecord?id=CVE-2026-64457 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64459 https://www.cve.org/CVERecord?id=CVE-2026-64459 Référence CVE CVE-2026-64460 https://www.cve.org/CVERecord?id=CVE-2026-64460 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 Référence CVE CVE-2026-64464 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-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=CVE-2026-64443 Référence CVE CVE-2026-64444 https://www.cve.org/CVERecord?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64446 https://www.cve.org/CVERecord?id=CVE-2026-64446 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 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-64472 https://www.cve.org/CVERecord?id=CVE-2026-64472 Référence CVE CVE-2026-64477 https://www.cve.org/CVERecord?id=CVE-2026-64477 Référence CVE CVE-2026-64478 https://www.cve.org/CVERecord?id=CVE-2026-64478 Référence CVE CVE-2026-64479 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-64447 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64451 https://www.cve.org/CVERecord?id=CVE-2026-64451 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64453 https://www.cve.org/CVERecord?id=CVE-2026-64453 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64457 https://www.cve.org/CVERecord?id=CVE-2026-64457 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64459 https://www.cve.org/CVERecord?id=CVE-2026-64459 Référence CVE CVE-2026-64460 https://www.cve.org/CVERecord?id=CVE-2026-64460 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 Référence CVE CVE-2026-64464 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-64447 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64451 https://www.cve.org/CVERecord?id=CVE-2026-64451 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64453 https://www.cve.org/CVERecord?id=CVE-2026-64453 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64457 https://www.cve.org/CVERecord?id=CVE-2026-64457 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64459 https://www.cve.org/CVERecord?id=CVE-2026-64459 Référence CVE CVE-2026-64460 https://www.cve.org/CVERecord?id=CVE-2026-64460 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 Référence CVE CVE-2026-64464 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64111 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64387 https://www.cve.org/CVERecord?id=CVE-2026-64387 Référence CVE CVE-2026-64414 https://www.cve.org/CVERecord?id=CVE-2026-64414 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-68128 https://www.cve.org/CVERecord?id=CVE-2026-68128 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68200 https://www.cve.org/CVERecord?id=CVE-2026-68200 Référence CVE CVE-2026-68264 https://www.cve.org/CVERecord?id=CVE-2026-68264 Référence CVE CVE-2026-68294 https://www.cve.org/CVERecord?id=CVE-2026-68294 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=CVE-2026-68363 Référence CVE CVE-2026-68426 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-64447 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64451 https://www.cve.org/CVERecord?id=CVE-2026-64451 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64453 https://www.cve.org/CVERecord?id=CVE-2026-64453 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64457 https://www.cve.org/CVERecord?id=CVE-2026-64457 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64459 https://www.cve.org/CVERecord?id=CVE-2026-64459 Référence CVE CVE-2026-64460 https://www.cve.org/CVERecord?id=CVE-2026-64460 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 Référence CVE CVE-2026-64464 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64446 https://www.cve.org/CVERecord?id=CVE-2026-64446 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64457 https://www.cve.org/CVERecord?id=CVE-2026-64457 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64463 https://www.cve.org/CVERecord?id=CVE-2026-64463 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64468 https://www.cve.org/CVERecord?id=CVE-2026-64468 Référence CVE CVE-2026-64469 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64446 https://www.cve.org/CVERecord?id=CVE-2026-64446 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64449 https://www.cve.org/CVERecord?id=CVE-2026-64449 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=CVE-2026-64450 Référence CVE CVE-2026-64452 https://www.cve.org/CVERecord?id=CVE-2026-64452 Référence CVE CVE-2026-64454 https://www.cve.org/CVERecord?id=CVE-2026-64454 Référence CVE CVE-2026-64455 https://www.cve.org/CVERecord?id=CVE-2026-64455 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64458 https://www.cve.org/CVERecord?id=CVE-2026-64458 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64468 https://www.cve.org/CVERecord?id=CVE-2026-64468 Référence CVE CVE-2026-64469 https://www.cve.org/CVERecord?id=CVE-2026-64469 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=

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: < 2.6.26, 5.10.261 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.96 ≤ 6.12.*, 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:56 UTC · CWE not yet assigned

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-64456 to remediation: access.redhat.com/CVE-2026-64456.
    Before
    remediation: access.redhat.com/CVE-2026-64456
    After
    remediation: access.redhat.com/CVE-2026-64456
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. 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 89 more
    After
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; 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-rt as a component of Red Hat Enterprise Linux 8; kernel-rt-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8; and 13 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.56.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.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.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.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.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.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.56.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.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 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-48800↗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-64456 · cve.blacktree.nl