CVE-2026-99640: ovl: do not let chattr change the casefold flag
In the Linux kernel, the following vulnerability has been resolved:
ovl: do not let chattr change the casefold flag
chattr +F or -F on an overlay directory can make the directory, or the whole mount, unusable. Lookups of the directory, and lookups in it, then fail. From code inspection, the caller only needs to own the directory. The upper filesystem must support casefolding: ext4 or f2fs with the casefold feature, or tmpfs with the casefold option.
chattr +F and -F set and clear FSCASEFOLDFL, the casefold flag of a directory. The flag enables casefolding (case-insensitive name lookup) for the directory. All directories of an overlay must match the casefold state that was recorded at mount time, and ovllookupsingle() enforces this:
- A lookup in a directory that does not match fails with -ESTALE. - A lookup of the directory itself fails with -EREMOTE.
ovlfileattrset() copies the directory up, which creates it in the upper layer if it only existed in a lower layer. It then passes FSCASEFOLDFL on to the upper filesystem. The upper filesystem accepts the change if the upper directory is empty, regardless of what the merged directory contains. The merged directory is the one that the user sees, with the names from the upper and the lower directories.
After the change the upper directory no longer matches the mount. If the directory is the root of the overlay, the whole mount is affected.
The flag can also change without chattr +F or -F. chattr reads all flags of a directory, changes one and writes all of them back. For a directory that only exists in a lower layer, overlayfs reads the flags from the lower filesystem. xfs with the ascii-ci feature reports FSCASEFOLDFL on every inode, but never sets SCASEFOLD, the inode flag that overlayfs compares with the mount. So its directories count as not casefolded. With a lower layer on such an xfs and an upper layer on ext4 with the casefold feature, chattr +A on a lower-only directory therefore sets FSCASEFOLDFL on the new, empty upper directory.
Reproduced as root on tmpfs and on ext4 with chattr +F or -F on an overlay directory whose upper directory was empty. Afterwards lookups below it failed with ESTALE, and lookups of the directory itself failed with EREMOTE. The chattr +A case was seen once, on a kernel with an earlier form of this patch that still passed the caller's flag on: lookups of the directory failed with EREMOTE.
Fix this by returning -EOPNOTSUPP if FSIOCSETFLAGS, the only call that can change the flag, asks for a casefold flag on a directory that does not agree with the casefold state of the mount. This also refuses the chattr +A case above.
[amir: check the flag against the casefold state of the mount instead of reading back the flags]
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.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto 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 - Compensating control
Change overlayfs ovl_fileattr_set() to return -EOPNOTSUPP for FS_IOC_SETFLAGS requests, preventing chattr from changing FS_CASEFOLD_FL on overlay directories.
Event History
Frequently Asked Questions
Which overlay mounts are exposed to this issue?
The upper filesystem must support casefolding: ext4 or f2fs with the casefold feature enabled, or tmpfs mounted with the casefold option. The issue applies when an overlay directory's casefold state can be changed after the overlay mount has recorded its expected state.
What level of access is needed to trigger the failure?
From code inspection, the caller only needs to own the affected directory. They can use chattr +F or chattr -F to set or clear the directory's casefold flag.
How can administrators recognize that an overlay mount has been affected?
Lookups in a directory whose casefold state no longer matches the state recorded at mount time fail with -ESTALE. Looking up that directory itself fails with -EREMOTE, and the directory or entire overlay mount may become unusable.