CVE-2026-80804 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux system administrators, and users of XFS file systems should assess their exposure and prioritize verification of affected systems. System administrators should review system configurations and apply patches as recommended by the Linux kernel maintainers. Linux kernel versions and XFS file system usage should be reviewed to identify potentially affected systems.

Why it matters

A vulnerability in the Linux kernel has been resolved, which could lead to a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.

• Verification of Linux kernel versions and XFS file system usage is necessary to determine potential exposure.
• System administrators should prioritize applying patches to prevent potential circular lock dependencies.
• Monitoring system logs is recommended to detect indicators of potential issues.

Technical summary

The vulnerability is caused by the NOFS context not being restored in the error path of xfs_trans_roll(). This can lead to a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim. The fix involves moving xfs_trans_set_context() before the error check to ensure the NOFS context is always restored. The vulnerability affects Linux kernel versions and XFS file system usage, potentially leading to system crashes or instability. Affected systems should be identified, and patches should be applied to prevent potential issues.

Defensive priority

Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems, especially those using XFS file systems.

Recommended defensive actions

• Review Linux kernel versions and XFS file system usage to identify potentially affected systems.
• Verify system configurations and apply patches as recommended by the Linux kernel maintainers.
• Monitor system logs for indicators of potential circular lock dependencies.
• Perform a thorough review of system configurations and apply necessary patches.
• Track exceptions and retest remediated assets.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and versions is not explicitly stated. The fix involves moving xfs_trans_set_context() before the error check to ensure the NOFS context is always restored.

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.