Local denial of service via FUSE inode livelock
Published Mar 20, 2021 · Updated Aug 3, 2024
Excessive iteration in Linux kernel FUSE before 5.11.8 allows local users to hang a CPU by provoking repeated lookup of a bad inode. The private fuse_make_bad implementation marks the inode bad without removing it from the inode cache, so iget5_locked retrieves it on every retry. The path requires local low-privileged access to a FUSE filesystem and can interrupt services without disclosing or altering data.
Summary
What happened
Excessive iteration in Linux kernel FUSE before 5.11.8 allows local users to hang a CPU by provoking repeated lookup of a bad inode. The private fuse_make_bad implementation marks the inode bad without removing it from the inode cache, so iget5_locked retrieves it on every retry. The path requires local low-privileged access to a FUSE filesystem and can interrupt services without disclosing or altering data.
The record
- CVE
- CVE-2021-28950
- Published
- Mar 20, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-834, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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