{"id":"CVE-2026-99415","summary":"ovl: set the revalidate flags after d_instantiate()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\novl: set the revalidate flags after d_instantiate()\n\nstat() of a file on an overlayfs mount triggers a kernel warning and\nfails with ECHILD if another task is creating that file at the same\ntime. This happens on an overlay with a FUSE upper layer, which is the\nlayer where overlayfs creates new files. Write access to a directory on\nsuch an overlay is all a user needs to run the two tasks.\n\nThe revalidate flags are DCACHE_OP_REVALIDATE and\nDCACHE_OP_WEAK_REVALIDATE. They tell path walk to call -\u003ed_revalidate()\nor -\u003ed_weak_revalidate() on a dentry, so that the filesystem can check\nthat the cached dentry is still valid. An overlay dentry only has one of\nthese flags if a dentry in one of its layers has it. FUSE dentries have\nthe first one.\n\nWhen a flag is set on an overlay dentry, path walk calls\novl_dentry_revalidate_common(). That function only expects a dentry\nwithout an inode in RCU walk, while the dentry is being destroyed. For\nsuch a dentry outside of RCU walk, it hits a WARN_ON() and\nreturns -ECHILD. So a negative overlay dentry must never have the flags\nset.\n\novl_instantiate() breaks this rule. When a task creates a file, the\noverlay dentry for the new name is hashed but still negative.\novl_instantiate() then works in this order:\n\n- It copies the flags from the new upper dentry to the overlay dentry.\n- It calls ovl_get_inode(), which can sleep in a getxattr request to the\n  FUSE server.\n- Only then does it call d_instantiate().\n\nA second task that looks up the name between the first step and the last\nfinds a negative dentry with the flags set and revalidates it.\n\nReproduced with a FUSE server that delays its getxattr reply: stat() of\na name that was being created hit the WARN_ON() and failed with ECHILD.\n\nFix this by setting the flags after d_instantiate().","modified":"2026-11-19T17:01:12.703600828Z","published":"2026-11-19T14:40:13.532Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99415.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3d92153206cebe95dc873a4b2b3d506ddf2271e7"},{"type":"WEB","url":"https://git.kernel.org/stable/c/75e89c0055c1d7f7eeb462995f11253ca5864f79"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7ecbeb1a84f2d099012ccd95a8a7588e1306cc46"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e876482d955476d0c066afda8273bfd38e0f65be"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99415.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99415"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"bccece1ead368149f90e05ad104dfbfda4422f5d"},{"fixed":"e876482d955476d0c066afda8273bfd38e0f65be"},{"fixed":"7ecbeb1a84f2d099012ccd95a8a7588e1306cc46"},{"fixed":"3d92153206cebe95dc873a4b2b3d506ddf2271e7"},{"fixed":"75e89c0055c1d7f7eeb462995f11253ca5864f79"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99415.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.7.0"},{"fixed":"6.12.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.61"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99415.json"}}],"schema_version":"1.9.2"}