CVE-2026-64320 Linux CVE debrief

Who should care

Linux administrators, security teams, and anyone responsible for managing Linux systems, especially those using nvmet, should assess their exposure and prioritize patching. This vulnerability could lead to sensitive data leakage, making it a significant concern for systems with nvmet targets exposed to untrusted networks or peers.

Why it matters

CVE-2026-64320 is a critical vulnerability in the Linux kernel's nvmet subsystem that allows for pre-authentication out-of-bounds heap reads. It is reachable by unauthenticated peers and can lead to sensitive data leakage. Linux administrators and security teams should prioritize patching and verify their exposure.

• Sensitive data leakage from the heap is possible.
• Unauthenticated peers can reach the nvmet target.
• Patching is required to prevent data leakage.
• Verification of affected versions and exposure is necessary.

Technical summary

The Linux kernel's nvmet subsystem is vulnerable to a pre-authentication out-of-bounds heap read in the Discovery Get Log Page. This issue arises from insufficient validation of the host-supplied Log Page Offset, which can cause sensitive data to be leaked from the heap. The vulnerability is reachable by any unauthenticated TCP/RDMA/FC peer that can reach the nvmet target. Affected Linux kernel deployments should be reviewed for exposure, and patches should be applied to prevent data leakage. The vulnerability has a CVSS score of 9.1 and is considered critical. Linux administrators and security teams should prioritize patching and verify their exposure to mitigate potential risks.

Defensive priority

High

Recommended defensive actions

• Review and apply patches from Linux kernel maintainers.
• Restrict access to nvmet targets to only trusted peers.
• Monitor for unusual activity or errors related to nvmet.
• Verify affected versions and upgrade to fixed versions.
• Perform a thorough review of system logs to detect potential exploitation attempts.
• Implement additional security measures such as network segmentation or access controls.
• Conduct a comprehensive risk assessment to identify and mitigate potential vulnerabilities.

Evidence notes

The CVE record and associated source item provide details on the vulnerability, including its description, affected versions, and references to patches. However, the corpus does not provide explicit information on exploitation or specific attacks.

Sources and references

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.