CVE-2026-97594 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems that utilize Landlock for security, including operators managing affected systems, platform administrators, vulnerability management teams, and security teams responsible for monitoring and incident response.

Why it matters

A use-after-free vulnerability in the Linux kernel's Landlock feature has been addressed. Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems that utilize Landlock for security should verify Linux kernel versions and configurations, monitor system logs, and update incident response plans to address potential use-after-free errors.

• Verify Linux kernel versions and configurations to ensure Landlock is properly configured and patched
• Monitor system logs for potential exploitation attempts
• Update incident response plans to include procedures for addressing potential use-after-free errors

Technical summary

The vulnerability occurs in the Linux kernel's Landlock feature, specifically in the current_check_refer_path() function. This function reads the parent directory of the source without holding a reference or lock on it, allowing for a potential use-after-free error. A process can trigger this after entering a Landlock domain that handles at least one filesystem access right. The process can then race a linkat(2) loop against rename(2) and rmdir(2).

Defensive priority

Apply patches or updates to affected Linux kernel versions to prevent potential use-after-free errors.

Recommended defensive actions

• Apply patches or updates to affected Linux kernel versions
• Review and update Linux kernel configurations to ensure Landlock is properly configured
• Monitor system logs for potential exploitation attempts
• Verify Linux kernel versions and configurations to ensure Landlock is properly configured and patched
• Update incident response plans to include procedures for addressing potential use-after-free errors
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and associated sources provide details on the vulnerability, including its description, CVSS score, and affected components. However, the corpus does not establish versions, exploitation, impact, or remediation beyond patching.

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.