CVE-2026-99131

xfs: fix capability check in xfs

  • High 8.2

Description

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()

Key facts

Published
28 Oct 2026
Last changed
31 Oct 2026
Assigned by
Linux
EPSS
0.45% likely to be exploited in the next 30 days, higher than 39.634% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.2CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding 29f994db0447104a7a52fb6495193c80007cb66a (affected)
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding e84bfb08016496ec5ce09a5ef9c813f23c060781 (affected)
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding 87881f816ab721d8a727cba20c36b9c71b489c8e (affected)
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding 19a1a22029ad3ae3604c763af6bd1195cb73648f (affected)
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding 7809ac0161c7c5f52ed348fb1ec683b2b454a83e (affected)
  • eba0549bc7d100691c13384b774346b8aa9cf9a9 up to but excluding e2f62a9744ebad3bcb6347a648e615026e9efeff (affected)
LinuxLinux
  • Default status: affected
  • 5.18 (affected)
  • 0 up to but excluding 5.18 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References