CVE-2026-99414 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

ovl: skip copy up of empty security.capability

ovl_copy_xattr() gives up if it can't read an attribute that listxattr() has named. An empty security.capability, which anybody has been able to store on any file for a long time, is such a case: it is listed, and getxattr() has nothing to return for it. A file in a lower layer that carries one can't be copied up: it can't be written to, renamed or have its mode changed.

There is nothing to copy if there are no data. Go on with the next one.

[amir: treat -EINVAL as no capability too, and do the same in
ovl_copy_up_meta_inode_data()]

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel's overlay filesystem implementation contains a logic flaw within the attribute copying mechanism that prevents files from being properly copied up when they contain empty extended attributes. Specifically, the function responsible for handling copy-up operations encounters an error condition when attempting to process security.capability attributes that are present but have no associated data payload. This issue stems from how the kernel handles negative return values during the retrieval of extended attribute metadata. When listxattr indicates the presence of a capability attribute, subsequent attempts to read its value using getxattr may fail if the attribute is empty or malformed in certain contexts. The original implementation treated this failure as a fatal error for the entire copy-up process rather than recognizing it as an indication that there was no actual data to transfer.

This vulnerability effectively creates a denial of service condition for file operations on affected overlay mounts. Any file residing in a lower layer that possesses such an empty security.capability attribute becomes immutable within the upper layer after being accessed or modified. Users and applications are unable to write to, rename, or change the mode permissions of these files because the kernel aborts the copy-up procedure entirely upon encountering the problematic attribute. This behavior persists across many Linux distributions where overlay filesystems are commonly used for containerization technologies such as Docker and Kubernetes, potentially impacting system stability and application availability in environments relying on persistent storage layers with pre-existing empty capability attributes.

From a technical classification perspective, this flaw aligns with CWE-754: Improper Check for Unusual or Exceptional Conditions. The code fails to properly validate the state of an attribute before treating its retrieval failure as a critical error. Furthermore, it relates to CWE-20: Improper Input Validation because the system does not adequately distinguish between a missing attribute and an empty but present one during the copy-up workflow. In terms of attack vectors, this could be leveraged in scenarios where attackers can influence file creation or modification on lower layers to embed such attributes, thereby locking files against legitimate administrative changes. This maps partially to ATT&CK technique T1485: Data Encrypted for Impact if viewed through the lens of rendering data inaccessible, although it is more accurately described as a local denial of service via resource exhaustion and file lockout rather than encryption-based impact.

The resolution involves modifying the ovl_copy_xattr function to recognize empty security.capability attributes as valid cases where no action is required. Instead of aborting the copy-up process due to an error code returned by getxattr, the kernel now treats specific negative return values like -EINVAL as indicators that there is simply no capability data to copy. This logic has also been extended to ovl_copy_up_meta_inode_data to ensure consistency across different metadata handling paths. By skipping empty attributes rather than failing on them, the overlay filesystem can successfully complete the copy-up operation for files containing these specific edge-case attributes.

To mitigate this vulnerability in environments where immediate patching is not feasible, administrators should audit lower-layer file systems for any existing security.capability extended attributes that are empty or zero-length. Removing such attributes from affected files before they are accessed by overlay-mounted containers can restore normal write and rename capabilities. Additionally, ensuring that container runtimes do not inadvertently create files with malformed capability sets during initialization helps prevent the recurrence of this issue. System administrators should apply kernel updates provided by their distribution vendors as soon as available to resolve the underlying logic error in the overlay filesystem driver.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00157

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!