CVE-2026-64438 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems that utilize the crypto: qat driver. Additionally, system administrators, security teams, and operators responsible for maintaining and securing Linux-based systems should be aware of this vulnerability and take necessary precautions to mitigate its impact.

Why it matters

This vulnerability requires immediate attention from Linux kernel developers, maintainers, and users. A use-after-free error can cause system instability, potential privilege escalation, and increased risk of DoS attacks or system compromise. Defenders should review and apply patches, update the Linux kernel, and monitor system logs for potential exploitation attempts.

• Potential system crashes or instability due to use-after-free errors
• Possible elevation of privileges or unauthorized access to sensitive data
• Increased risk of denial-of-service (DoS) attacks or system compromise

Technical summary

The vulnerability exists in the Linux kernel's crypto: qat driver. A use-after-free error occurs when adf_disable_sriov() is called, causing a concurrently scheduled or already queued worker to dereference freed memory. This can lead to system instability, potential privilege escalation, and increased risk of DoS attacks or system compromise. The issue arises from the destruction of per-VF mutexes and freeing of vf_info without stopping new VF2PF work or waiting for in-flight workers to complete. To address this, a PF-local flag, vf2pf_disabled, can be implemented to gate work queueing, worker processing, and interrupt re-enabling during teardown.

Defensive priority

High

Recommended defensive actions

• Review and apply the provided patches to address the vulnerability
• Ensure that the Linux kernel is updated to a version that includes the fix
• Monitor system logs for potential exploitation attempts
• Perform a thorough review of system configurations and network architecture to identify potential vulnerabilities
• Implement compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions and retest remediated assets to ensure the vulnerability is fully resolved
• Continuously monitor for new information about the vulnerability and adjust defensive measures as needed

Evidence notes

The CVE record and source item provide details about the vulnerability, including a description of the issue and affected versions. However, the corpus does not establish specific exploitation or impact, and remediation priority is not explicitly stated.

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.