CVE-2026-90263btrfs: check if root is readonly when setting posix acl
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% 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: btrfs: check if root is readonly when setting posix acl For a filesystem which has btrfs read-only property set to true, all write operations including acl and xattr should be denied. However, acl can still be set even if btrfs ro property is true. This happens because no function on the set_acl code path checks the root is readonly or not. It was checked in btrfs_setxattr_trans() but got removed in commit 353c2ea735e4 ("btrfs: remove redundant readonly root check in btrfs_setxattr_trans") That commit didn't check if all the callers properly check the root's read-only flag. A previous fix is commit b51111271b03 ("btrfs: check if root is readonly while setting security xattr"). Always check if the root is read-only before performing the set acl operation.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < f3e6b504a79d8e90bb7aa8a03a42dc2b51dcc4c4
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < 20b2c2f3316e82a76ae3358c0bd45824f50f3fd5
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < dc3a6e90a0a6350a6d43fed9f005f54171809580
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < ce8103676f4d4b13e1f087fcfb34f80774d30be2
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < d5602f96ff1e266f069b4d0d94f441050e057e06
- affected 353c2ea735e4b54fb6250861e67b51b1bcb47198 – < 01c2f41fc441f75b3f9326443372faceb1cb6638
- affected 5.2
- unaffected < 5.2
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/f3e6b504a79d8e90bb7aa8a03a42dc2b51dcc4c4 (opens in a new tab)
- https://git.kernel.org/stable/c/20b2c2f3316e82a76ae3358c0bd45824f50f3fd5 (opens in a new tab)
- https://git.kernel.org/stable/c/dc3a6e90a0a6350a6d43fed9f005f54171809580 (opens in a new tab)
- https://git.kernel.org/stable/c/ce8103676f4d4b13e1f087fcfb34f80774d30be2 (opens in a new tab)
- https://git.kernel.org/stable/c/d5602f96ff1e266f069b4d0d94f441050e057e06 (opens in a new tab)
- https://git.kernel.org/stable/c/01c2f41fc441f75b3f9326443372faceb1cb6638 (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-81856 (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-90263)Record last updated .