CVE-2026-99424
ovl: set OVL_WHITEOUTS before publishing the upper dir
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ovl: set OVL_WHITEOUTS 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 OVL_I(inode)->cache without looking at its refcount, while files opened in merged mode still use it. ovl_copy_up_workdir() publishes the upper dentry before it sets OVL_WHITEOUTS, and ovl_dir_open() 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 OVL_WHITEOUTS before ovl_inode_update(), so that ovl_dir_reset() agrees with ovl_dir_open(), and by testing OVL_TYPE_MERGE() of the path type in ovl_dir_open(), 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 OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: b79e05aaa166755fafbf02db275175edb5175df8 to < 43ad4a3090e1c2a0c34e9802882b42c5c078d556; affected: b79e05aaa166755fafbf02db275175edb5175df8 to < 7805739ce4577f2c53f5a30be2d48e83e91c63bc; affected: b79e05aaa166755fafbf02db275175edb5175df8 to < ea5327a9228bfd1609e54f1fca50786e8f963da5; affected: b79e05aaa166755fafbf02db275175edb5175df8 to < cbec8610ec5aaf35df50094ff639febc23f20773 | See vendor advisory |
| LinuxLinux | affected: 4.15; unaffected: 0 to < 4.15; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99424
- https://git.kernel.org/stable/c/43ad4a3090e1c2a0c34e9802882b42c5c078d556
- https://git.kernel.org/stable/c/7805739ce4577f2c53f5a30be2d48e83e91c63bc
- https://git.kernel.org/stable/c/ea5327a9228bfd1609e54f1fca50786e8f963da5
- https://git.kernel.org/stable/c/cbec8610ec5aaf35df50094ff639febc23f20773