PT-2026-151630

CVE-2026-99419

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
ovl: do not copy up a dentry that was removed
A change to a removed file through an open descriptor replaces whatever has its old name in the upper layer.
Copy up must only create a name in the upper directory, never replace one. After an unlink, an rmdir or a rename over a lower dentry, a dentry that an open file keeps alive still has its old parent and name, but in the upper directory that name is now a whiteout or a new object. ovl copy up workdir() renames the copy over it, which brings back the removed object and destroys whatever took its name.
An unprivileged user opened a lower FIFO and unlinked it, root created a file at that name, and fchmod on the old descriptor replaced the file of root with the FIFO.
Fix this by looking up the target name of the rename in ovl copy up workdir() with LOOKUP EXCL, so that copy up fails with -EEXIST if the name is taken, as copy up with O TMPFILE already does when it links the copy to the name.
[amir: use LOOKUP EXCL instead of relying on d unhashed()]
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾