ubifs: Fix races between xattr_{set|get} and listxattr operations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Fix races between xattr_{set|get} and listxattr operations
UBIFS may occur some problems with concurrent xattr_{set|get} and listxattr operations, such as assertion failure, memory corruption, stale xattr value[1].
Fix it by importing a new rw-lock in @ubifs_inode to serilize write operations on xattr, concurrent read operations are still effective, just like ext4.
[1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com
From the CVE record · Linux
UBIFS in the Linux kernel has races between concurrent xattr set/get and listxattr operations. When those operations overlap, they can cause an assertion failure, memory corruption, or a stale xattr value. The input does not specify authentication or user-interaction requirements.
Anyone running a Linux kernel that uses UBIFS should check whether their kernel includes the fix; affected versions are not specified.