Linux kernel file modification denial in overlayfs xattr copy-up
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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()]
From the CVE record · Linux
The Linux kernel’s overlayfs copy-up can fail when a file in a lower layer has an empty security.capability attribute. Anyone able to place that attribute on a file can prevent the file from being written, renamed, or having its mode changed when overlayfs tries to copy it up. The input does not specify whether this can be triggered over a network or requires authentication or user interaction.
Engineers running the Linux kernel with overlayfs should check their systems; affected versions are not specified.