CVE-2026-99131xfs: fix capability check in xfs
- 8.2HighCVSS base score
- 0.45%Exploitation in 30 daysEPSS · top 60% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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()
Timeline
ID reserved
By Linux
- 33 days later
· 33 days later
Published
- 3 days later
· 3 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| NVDNVD · Received | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.45% · top 60% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < 29f994db0447104a7a52fb6495193c80007cb66a
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < e84bfb08016496ec5ce09a5ef9c813f23c060781
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < 87881f816ab721d8a727cba20c36b9c71b489c8e
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < 19a1a22029ad3ae3604c763af6bd1195cb73648f
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < 7809ac0161c7c5f52ed348fb1ec683b2b454a83e
- affected eba0549bc7d100691c13384b774346b8aa9cf9a9 – < e2f62a9744ebad3bcb6347a648e615026e9efeff
- affected 5.18
- unaffected < 5.18
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/29f994db0447104a7a52fb6495193c80007cb66a (opens in a new tab)
- https://git.kernel.org/stable/c/e84bfb08016496ec5ce09a5ef9c813f23c060781 (opens in a new tab)
- https://git.kernel.org/stable/c/87881f816ab721d8a727cba20c36b9c71b489c8e (opens in a new tab)
- https://git.kernel.org/stable/c/19a1a22029ad3ae3604c763af6bd1195cb73648f (opens in a new tab)
- https://git.kernel.org/stable/c/7809ac0161c7c5f52ed348fb1ec683b2b454a83e (opens in a new tab)
- https://git.kernel.org/stable/c/e2f62a9744ebad3bcb6347a648e615026e9efeff (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-111883 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99131)Record last updated .