vfs: Don't leak disconnected dentries on umount
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.301, 5.10.246, 5.15.196, 6.1.158, 6.6.114, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: vfs: Don't leak disconnected dentries on umount When user calls open_by_handle_at() on some inode that is not cached, we will create disconnected dentry for it. If such dentry is a directory, exportfs_decode_fh_raw() will then try to connect this dentry to the dentry tree through reconnect_path(). It may happen for various reasons (such as corrupted fs or race with rename) that the call to lookup_one_unlocked() in reconnect_one() will fail to find the dentry we are trying to reconnect and instead create a new dentry under the parent. Now this dentry will not be marked as disconnected although the parent still may well be disconnected (at least in case this inconsistency happened because the fs is corrupted and .. doesn't point to the real parent directory). This creates inconsistency in disconnected flags but AFAICS it was mostly harmless. At least until commit f1ee616214cb ("VFS: don't keep disconnected dentries on d_anon") which removed adding of most disconnected dentries to sb->s_anon list. Thus after this commit cleanup of disconnected dentries implicitely relies on the fact that dput() will immediately reclaim such dentries. However when some leaf dentry isn't marked as disconnected, as in the scenario described above, the reclaim doesn't happen and the dentries are "leaked". Memory reclaim can eventually reclaim them but otherwise they stay in memory and if umount comes first, we hit infamous "Busy inodes after unmount" bug. Make sure all dentries created under a disconnected parent are marked as disconnected as well.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in b5abafd0aa8d7bcb935c8f91e4cfc2f2820759e4; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in 20863bb7fbb016379f8227122edfabc5c799bc79; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in 8004d4b8cbf1bd68a23c160d57287e177c82cc69; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in 7e0c8aaf4e28918abded547a5147c7d52c4af7d2; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in cebfbf40056a4d858b2a3ca59a69936d599bd209; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in 620f3b0ede9c5cb4976cd0457d0b04ad551e5d6b; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in eadc49999fa994d6fbd70c332bd5d5051cc42261; From f1ee616214cb22410e939d963bbb2349c2570f02 · fixed in 56094ad3eaa21e6621396cc33811d8f72847a834
- Linux Linux
4.16
- KernelLinux
From 4.16.0 · fixed in 5.4.301; From 5.5.0 · fixed in 5.10.246; From 5.11.0 · fixed in 5.15.196; From 5.16.0 · fixed in 6.1.158; From 6.2.0 · fixed in 6.6.114; From 6.7.0 · fixed in 6.12.55; From 6.13.0 · fixed in 6.17.5
References 8
git.kernel.org
- stable/c/b5abafd0aa8d7bcb935c8f91e4cfc2f2820759e4
- stable/c/20863bb7fbb016379f8227122edfabc5c799bc79
- stable/c/8004d4b8cbf1bd68a23c160d57287e177c82cc69
- stable/c/7e0c8aaf4e28918abded547a5147c7d52c4af7d2
- stable/c/cebfbf40056a4d858b2a3ca59a69936d599bd209
- stable/c/620f3b0ede9c5cb4976cd0457d0b04ad551e5d6b
- stable/c/eadc49999fa994d6fbd70c332bd5d5051cc42261
- stable/c/56094ad3eaa21e6621396cc33811d8f72847a834