New RefluXFS Linux flaw lets attackers gain root privileges
A nine-year-old race condition in the Linux kernel’s XFS filesystem, tracked as **CVE-2026-64600** and dubbed **RefluXFS**, lets a local attacker overwrite…
By Dillip Chowdary • Aug 07, 2026 • Source: BleepingComputer
A nine-year-old race condition in the Linux kernel’s XFS filesystem, tracked as **CVE-2026-64600** and dubbed **RefluXFS**, lets a local attacker overwrite protected files and escalate to root. The flaw sits in long-standing kernel filesystem code rather than a new feature surface, which explains both its age and the breadth of systems that may still carry the weak path until patched.
Technically, **XFS** is a journaling filesystem used widely on servers and enterprise Linux hosts. A race condition means two concurrent operations can hit a shared state in the wrong order, so a check that a file or path is safe can pass before an attacker swaps or rebinds the target. That window is what lets a local process write into files that should stay protected and, from there, obtain root privileges.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
For engineers and builders, the risk is local privilege escalation on hosts that already allow untrusted or multi-tenant local access: shared CI runners, developer workstations, containers that share a host kernel, and any box where a low-privilege account can run code. Root from a race in filesystem plumbing is high impact because it bypasses application-level controls and often lands full control of the machine.
In market terms, this sits in the familiar class of Linux kernel local-privilege bugs that matter more as cloud, containers, and multi-user machines concentrate workloads on one kernel. **BleepingComputer** is reporting the issue under the **RefluXFS** name; operators will treat it like other long-lived VFS/XFS races—inventory where XFS is mounted, who can run local code, and how quickly vendor kernels ship the fix.
Practical takeaway: treat **CVE-2026-64600** as a priority local-root issue on XFS-backed systems; limit who can execute on those hosts, keep kernel packages on a short patch cycle, and watch for distro advisories that name this CVE. Next to track is whether public exploit detail appears and which enterprise and cloud images still ship unpatched kernels with XFS in the default path.
Advertisement
🔎 More interesting news
- Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
- ByteDance aims to rival Anthropic with new model reaching up to 10T parameters
- Indirect Prompt Injection Exploits GitHub's AI Agent to Leak Private Repository Data
- Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models
- Today's full Tech Pulse briefing →