/00 — boot sequence

Hello.

Article

RefluxFS CVE-2026-64600: 9-Year Linux Kernel XFS Race Condition Lets Users Gain Root on RHEL

July 26, 2026•5 min read
security linux kernel cve-2026-64600 xfs qualys

A nine-year-old race condition in the Linux kernel XFS filesystem lets any local user escalate to root on default enterprise Linux installations. Tracked as CVE-2026-64600 and dubbed RefluxFS, the flaw affects every kernel since version 4.11 (2017) and impacts an estimated 16.4 million systems worldwide. Qualys researchers discovered it using AI-assisted code analysis with Anthropic's Claude model, marking a notable milestone in AI-accelerated vulnerability research.

Vulnerability Details (CVSS 7.8, Emergency Priority)

CVE-2026-64600 is a local privilege escalation vulnerability in the XFS filesystem copy-on-write (CoW) path. An unprivileged local attacker can overwrite any readable file on a reflink-enabled XFS volume — including /etc/passwd or SUID-root binaries — gaining persistent root access. The exploit works under standard hardening (SELinux Enforcing, containers, KASLR, SMEP/SMAP) and leaves no kernel log artifacts.

PropertyValue
CVE IDCVE-2026-64600
CVSS 3.17.8 (High) — Qualys rates Emergency Priority
Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow (ordinary user)
User InteractionNone
Affected KernelsLinux 4.11+ (2017-present)
Fixed KernelsPatched in stable/longterm branches, July 2026

Impact Assessment

The vulnerability is unusually severe for a local LPE:

  • Default installations affected: RHEL 8/9/10, CentOS Stream, Oracle Linux, Rocky Linux, AlmaLinux, Amazon Linux 2023, and Fedora Server all use XFS with reflink=1 by default.
  • 16.4 million systems: Qualys CyberSecurity Asset Management telemetry estimates this exposure across internet-facing and enterprise workloads.
  • No practical mitigations: SELinux, seccomp, container namespaces, kernel lockdown, and memory protections (KASLR, SMEP, SMAP) do not block the exploit because the bug operates at the filesystem block-allocation layer.
  • Persistence across reboots: On-disk modifications survive restart; no kernel log entries are generated.
  • AI-assisted discovery: Qualys TRU used Anthropic's Claude Mythos Preview to identify the race condition, then human researchers validated and weaponized it — a hybrid workflow they call "responsible AI-accelerated research."

Affected Systems

Any Linux distribution meeting all three criteria is vulnerable:

  1. Kernel version 4.11 or later (released April 2017)
  2. XFS filesystem with reflink=1 (the default on RHEL-family distros)
  3. A writable directory for the attacker (e.g., /tmp, /home/user, /var/tmp)

Confirmed affected distributions (non-exhaustive):

  • RHEL 8, 9, 10
  • CentOS Stream 8, 9, 10
  • Oracle Linux 8, 9, 10
  • Rocky Linux 8, 9, 10
  • AlmaLinux 8, 9, 10
  • Amazon Linux 2023 and Amazon Linux 2 (AMIs from Dec 2022 onward)
  • Fedora Server 31+
  • Debian, Ubuntu, SUSE: only if XFS was manually selected at install with reflink=1

Mitigation & Patching

Immediate action required: Apply vendor kernel updates and reboot. No configuration workaround exists.

DistributionAdvisoryFixed Package
RHEL 8RHSA-2026:39179kernel-4.18.0-553.30.1.el8_10
RHEL 9RHSA-2026:41062kernel-5.14.0-427.44.1.el9_4
RHEL 10RHSA-2026:41063kernel-6.6.0-24.el10
Oracle Linux 8ELSA-2026-39494kernel-uek-5.15.0-200.163.5
Oracle Linux 9ELSA-2026-39494kernel-uek-6.8.0-200.163.5
Amazon Linux 2023ALAS2026-1234kernel-6.1.100-140.183.amzn2023
Fedora 40/41FEDORA-2026-085c9e92a4kernel-6.10.x
AlmaLinux/Rocky 8, 9, 10ALSA-2026:39179 / RLSA-2026:39179Respective kernel packages

Verification: After reboot, confirm the fix with uname -r and check your vendor's security advisory for the exact fixed version. Qualys provides detection QIDs (e.g., QID 387841 for the vulnerability itself, plus distribution-specific QIDs listed in their advisory).

Detection

Since exploitation leaves no kernel logs, detection relies on:

  1. Vulnerability scanning: Qualys VMDR QIDs 387841, 6600012, 6053109, 6053104, 6052390, 6052332, 944816, 6052326, 289032, 6052307, 6052294, 6052291, 944834, 963680, 963688, 963682, 944802
  2. File integrity monitoring: Watch for unexpected changes to /etc/passwd, /etc/shadow, SUID binaries, or SSH authorized_keys files
  3. Auditd rules: Monitor ioctl(FICLONE) and O_DIRECT write patterns on XFS mounts (high false-positive rate)
  4. Post-exploitation forensics: Check file ctime/mtime discrepancies on critical system files; the on-disk modification timestamp will not match the inode change time

Technical Root Cause (Simplified)

The bug is a classic time-of-check-time-of-use (TOCTOU) race in XFS's reflink CoW path:

  1. Process A opens a target file (e.g., /etc/passwd) with O_DIRECT and issues a write
  2. XFS starts CoW: allocates a new block, prepares to remap the file extent
  3. To avoid deadlock, XFS drops the inode lock while waiting for log space
  4. Process B concurrently writes to the same reflinked file, completes its own CoW cycle, and drops the original block's refcount to 1
  5. Process A re-acquires the lock, sees refcount=1 (stale value from before the lock drop), assumes the block is private, and writes directly to the original physical block — corrupting the target file on disk

Because O_DIRECT bypasses the page cache, the write persists immediately. No revalidation occurs. The fix adds a revalidation step after re-acquiring the inode lock to confirm the physical block address hasn't changed.

Frequently Asked Questions

Q: Does this affect containers? A: Yes. The vulnerability operates at the filesystem block layer, below container namespaces. A compromised container with a writable XFS mount can escape to host root.

Q: Can SELinux block this? A: No. Qualys validation confirms the exploit succeeds under SELinux Enforcing mode on default RHEL policies.

Q: Is there a live-patching option (Kpatch, KernelCare, etc.)? A: Vendor live patches may become available, but a full reboot is required to ensure the new kernel is running. Qualys recommends rebooting after patching.

Q: What about systems using ext4, btrfs, or ZFS? A: Not affected. The bug is specific to XFS's reflink implementation. Systems using other filesystems for / are safe.

Q: How was AI involved in the discovery? A: Qualys TRU prompted Anthropic's Claude Mythos Preview to hunt for Dirty COW-style race conditions in the Linux kernel's memory-management and filesystem subsystems. The model identified the XFS reflink race and produced a working PoC. Human researchers then verified, refined, and coordinated disclosure. Qualys emphasizes this was expert-supervised, not autonomous AI vulnerability hunting.

Q: Where can I find the technical advisory and PoC details? A: Qualys advisory: https://blog.qualys.com/vulnerabilities-threat-research/2026/07/22/refluxfs-a-linux-kernel-local-privilege-escalation-to-root-in-xfs-cve-2026-64600 Technical details: https://cdn2.qualys.com/advisory/2026/07/22/RefluXFS.txt

Key Takeaways

  1. Patch immediately: This is not a theoretical vulnerability. Reliable exploits exist, affected systems number in the millions, and no mitigation works.
  2. Default configs are the risk: Enterprise Linux defaults (XFS + reflink) maximize exposure. Audit your fleet for XFS root filesystems.
  3. AI-assisted research is maturing: The Qualys-Anthropic collaboration demonstrates a reproducible workflow where LLMs accelerate expert discovery without replacing human validation.
  4. Filesystem-layer bugs bypass traditional hardening: Memory protections, syscall filters, and MAC systems operate above the block layer. Defense-in-depth must include filesystem integrity monitoring.
  5. Reboot is non-negotiable: Kernel patches only take effect after restart. Schedule maintenance windows now.

Sources:

Automated Transmission

This entry was synthesized and populated dynamically using native API integrations.

Resources & Links