Linux kernel group quota bypass in XFS capability checks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eba0549bc7d100691c13384b774346b8aa9cf9a9 · < e2f62a9744ebad3bcb6347a648e615026e9efeff| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix capability check in xfs
An user reported a bug where he managed to evade group's quota by changing a file's gid to a different group id the same user belonged to, even though quotas were enforced on both gids and the file's size was big enough to exceed the quota's hardlimit.
Commit eba0549bc7d1 replaced a capable() call by a has_capability_noaudit() to prevent unnecessary selinux audit messages. Turns out that both calls have slightly different semantics even though their documentation seems similar. Where in a nutshell:
capable() - Tests the task's effective credentials has_ns_capability_noaudit() - Tests the task's real credentials
This most of the time has no practical difference but in some cases like changing attrs (specifically group id in this case) through a NFS client this will allow the quota code to use XFS_QMOPT_FORCE_RES, effectively bypassing quota accounting checks.
Using instead ns_capable_noaudit() should fix this issue and prevent selinux audit messages.
This also fix the remaining calls to has_capability_noaudit()
From the CVE record · Linux
The Linux kernel’s XFS capability check can allow a user to bypass group quota checks when changing a file’s group ID to another group they belong to. This can occur through an NFS client even when quotas are enforced on both groups; the input does not specify affected versions.
Engineers running Linux systems with XFS group quotas, particularly where users access files through NFS clients, should check their kernel versions against the vendor advisory.