Local privilege escalation via UBIFS whiteout double free
Published Feb 26, 2025 · Updated Aug 5, 2026
Double free in Linux kernel UBIFS allows local users to crash the host or execute kernel code through a whiteout rename on a writable volume. When ubifs_budget_space fails in rename_whiteout, the error path frees whiteout_ui->data before iput reaches ubifs_free_inode and frees the same allocation again. Directory write access on a mounted writable UBIFS volume is sufficient; allocator corruption can panic the kernel or permit control-flow hijacking.
Summary
What happened
Double free in Linux kernel UBIFS allows local users to crash the host or execute kernel code through a whiteout rename on a writable volume. When ubifs_budget_space fails in rename_whiteout, the error path frees whiteout_ui->data before iput reaches ubifs_free_inode and frees the same allocation again. Directory write access on a mounted writable UBIFS volume is sufficient; allocator corruption can panic the kernel or permit control-flow hijacking.
The record
- CVE
- CVE-2021-47638
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.9
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <14276d38c89a170363e90b6ac0a53c3cf61b87fc
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <2ad07009c459e56ebdcc089d850d664660fdb742
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <2b3236ecf96db7af5836e1366ce39ace8ce832fa
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <40a8f0d5e7b3999f096570edab71c345da812e3e
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <6d7a158a7363c1f6604aa47ae1a280a5c65123dd
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <8b3c7be16f3f4dfd6e15ac651484e59d3fa36274
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <a90e2dbe66d2647ff95a0442ad2e86482d977fd8
- Affected versionversion=9e0a1fff8db56eaaebb74b4a3ef65f86811c4798 <b9a937f096e608b3368c1abc920d4d640ba2c94f
What conditions does exploitation require?
What is affected?
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.
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