PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64456 Linux CVE debrief

A vulnerability in the Linux kernel's hwrng: virtio component can cause memory safety issues and potential cross-boundary leaks when a malicious or buggy virtio-rng backend over-reports used.len, allowing the driver to read past the end of the inline array into adjacent slab contents. This can lead to memory safety issues and potential cross-boundary leaks, emphasizing the need for high-priority assessment and remediation for Linux systems using the affected hwrng: virtio component. The vulnerability is caused by the hwrng: virtio component not properly clamping the device-reported used.len at copy_data(), allowing a malicious or buggy virtio-rng backend to steer the memcpy() past

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-25
Original CVE updated
2026-10-19
Advisory published
2026-07-25
Advisory updated
2026-10-19

Who should care

Linux system administrators, security teams, and developers using the affected hwrng: virtio component should assess exposure and prioritize remediation due to potential memory safety issues and cross-boundary leaks. The vulnerability can be triggered by a malicious or buggy virtio-rng backend, emphasizing the need for high-priority assessment and remediation for Linux systems using the affected hwrng: virtio component. Linux system administrators, and

Why it matters

The CVE-2026-64456 vulnerability in the Linux kernel's hwrng: virtio component requires high-priority assessment and remediation due to potential memory safety issues and cross-boundary leaks.

  • Memory safety issues can occur due to reading past the end of the inline array into adjacent slab contents.
  • Potential cross-boundary leaks may allow sensitive data exposure.
  • Verification of system configurations and updates to unaffected versions is necessary.
  • Remediation priority is high due to the potential for memory safety issues and data exposure.

Technical summary

The vulnerability is caused by the hwrng: virtio component not properly clamping the device-reported used.len at copy_data(), allowing a malicious or buggy virtio-rng backend to steer the memcpy() past the end of the inline array into adjacent kmalloc-1k slab bytes. This can lead to memory safety issues and potential cross-boundary leaks, emphasizing the need for high-priority assessment and remediation for Linux systems using the affected hwrng: virtio component. The vulnerability can be triggered by a and requires

Defensive priority

High-priority assessment and remediation recommended for Linux systems using the affected hwrng: virtio component.

Recommended defensive actions

  • Assess exposure and prioritize remediation for Linux systems using the affected hwrng: virtio component
  • Review and apply patches from Linux vendors
  • Monitor for potential memory safety issues and cross-boundary leaks
  • Verify system configurations and update to unaffected versions if necessary
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to source code changes. The Linux kernel's hwrng: virtio component is vulnerable to memory safety issues and potential cross-boundary leaks due to improper clamping of device-reported used.len at copy_data(). The vulnerability can be triggered by a malicious or buggy virtio-rng backend, emphasizing the need for high-priority assessment and remediation for Linux systems using the affected hwrng: virtio

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64456 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64456

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64456 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64456

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/64xxx/CVE-2026-64456.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3aa3e89cf80721c8d382b4c1a2b70a0449dad4a5

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/63335e7b638ae70028ae285bb95153874a8bc852

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2e788948ff2a13358a303af112497a63201c5739

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/fde19b0d4eeabae042519313c843fe6f27d41e9d

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/81dd21b5f0c299cc7b5bf84f04a61938559d20e6

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/285e17c44e3873a73460f294acbd64018ff64385

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/92d5736a62040ec1cfff23ea57e6599301690ad5

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.