CVE-2026-99639: ovl: fix whiteout creation in casefolded directories

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ovl: fix whiteout creation in casefolded directories

unlink and rmdir fail with EINVAL on an overlay with casefolded (case-insensitive) layers, if the name exists in a lower layer. Casefolded layers need CONFIGUNICODE. Root can mount such an overlay, and so can an unprivileged user in a user namespace, with tmpfs layers.

Overlayfs does not change a lower layer. To remove a name that exists there, it hides the name with a marker file, a whiteout. It creates the whiteout in the work directory, a scratch directory on the upper filesystem, and renames it over the name in the upper directory:

- ovlwhiteout() creates the whiteout with mknod, or as a hard link to an earlier whiteout. - ovlcleanupandwhiteout() then prepares the rename with startrenamingtwodentries(), which returns -EINVAL if the source or the target dentry is unhashed, that is, not in the dentry hash table.

With casefolded directories, both dentries can be unhashed:

- The target. Lookup in a casefolded directory leaves a negative dentry unhashed, so the rename target is unhashed if the name does not exist in the upper directory. - The source, which is the new whiteout. tmpfs hashes a dentry when mknod or link makes it positive, but ext4 does not, so on ext4 the source is unhashed as well.

The cleanup after the failure also refuses an unhashed dentry, so on ext4 the whiteout is left behind in the work directory.

Reproduced with rm and rmdir on casefolded tmpfs and ext4 layers, also as uid 1000 in a user namespace.

Fix this by creating the whiteout with ovlcreatetemp(), which repeats the lookup if the new dentry is unhashed. Prepare the rename with startrenamingdentry(), which looks up the target name with the directories locked. The caller looked the name up without a lock, so return -ESTALE if the name now refers to a different inode.

[amir: pass the name used for lookup instead of taking a name snapshot]

Affected Software

3 affected componentsFixes available
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1
  3. Compensating control

    In OverlayFS, create the whiteout with ovl_create_temp() instead of ovl_whiteout().

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using OverlayFS with casefolded, case-insensitive layers are affected when removing names that exist only in a lower layer. Casefolded layers require CONFIG_UNICODE.

2

Can an unprivileged user trigger the failure?

Yes. An unprivileged user in a user namespace can mount an affected overlay when using tmpfs layers; root can also mount such an overlay.

3

What symptom indicates that an overlay may be affected?

Attempts to unlink a file or remove a directory can fail with EINVAL when the name exists in a lower layer but not in the upper layer. The failure occurs while OverlayFS tries to create and rename a whiteout marker to hide the lower-layer name.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203