System hang via missing FUSE inode reference
Published Jan 13, 2026 · Updated Jan 13, 2026
Deadlock in Linux Kernel 6.9 and affected stable branches allows local users to hang the system through FUSE readahead reclaim. fuse_prepare_release() skips taking an inode reference when the FUSE server lacks open support, allowing reclaim to evict that inode while its readahead folio remains locked. Exploitation requires low-privileged local access, an active FUSE server without open support, an in-flight readahead request, and server-triggered reclaim; the resulting circular wait leaves kernel work blocked indefinitely.
Summary
What happened
Deadlock in Linux Kernel 6.9 and affected stable branches allows local users to hang the system through FUSE readahead reclaim. fuse_prepare_release() skips taking an inode reference when the FUSE server lacks open support, allowing reclaim to evict that inode while its readahead folio remains locked. Exploitation requires low-privileged local access, an active FUSE server without open support, an in-flight readahead request, and server-triggered reclaim; the resulting circular wait leaves kernel work blocked indefinitely.
The record
- CVE
- CVE-2025-68821
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.9
- Affected versionversion=7d38aa079ed859b73f4460aab89c7619b04963b8 <4703bc0e8cd3409acb1476a70cb5b7ff943cf39a
- Affected versionversion=a39f70d63f4373a598820d9491719e44cd60afe9
- Affected versionversion=c7ec75f3cbf73bd46f479f7d6942585f765715da <cf74785c00b8b1c0c4a9dd74bfa9c22d62e2d99f
- Affected versionversion=e26ee4efbc79610b20e7abe9d96c87f33dacc1ff <bd5603eaae0aabf527bfb3ce1bb07e979ce5bd50
- Affected versionversion=e26ee4efbc79610b20e7abe9d96c87f33dacc1ff <e0d6de83a4cc22bbac72713f3a58121af36cc411
- Affected versionversion=e26ee4efbc79610b20e7abe9d96c87f33dacc1ff <fbba8b00bbe4e4f958a2b0654cc1219a7e6597f6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo