Bug 2536300 (CVE-2026-90263) - CVE-2026-90263 kernel: btrfs: check if root is readonly when setting posix acl
Summary: CVE-2026-90263 kernel: btrfs: check if root is readonly when setting posix acl
Keywords:
Status: NEW
Alias: CVE-2026-90263
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 17:16 UTC by OSIDB Bzimport
Modified: 2026-10-13 13:40 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 17:16:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.