CVE-2026-99424: ovl: set OVL_WHITEOUTS before publishing the upper dir
In the Linux kernel, the following vulnerability has been resolved:
ovl: set OVLWHITEOUTS before publishing the upper dir
Listing a directory while it is copied up causes a use-after-free of the readdir cache.
A merge directory must never be iterated as a real upper directory: that mode frees the cache in OVLI(inode)->cache without looking at its refcount, while files opened in merged mode still use it. ovlcopyupworkdir() publishes the upper dentry before it sets OVLWHITEOUTS, and ovldiropen() samples both without a lock, so an open between the two stores finds the upper directory and takes it for a real one.
With a delay between the two stores, an unprivileged process that listed a directory during its copy-up saw only "." and "..", and its next getdents freed the readdir cache of another descriptor.
Fix this by setting OVLWHITEOUTS before ovlinodeupdate(), so that ovldirreset() agrees with ovldiropen(), and by testing OVLTYPEMERGE() of the path type in ovldiropen(), so that an open that observes the upper dentry never iterates a merge dir as a real dir, regardless of the order in which it observes the flag.
[amir: test OVLTYPEMERGE() instead of smprmb() in ovldiropen()]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Compensating control
In OverlayFS, set OVL_WHITEOUTS before calling ovl_inode_update(), so ovl_dir_open() cannot treat a merge directory as a real upper directory.