Skip to main content
VulnerabilityPublished Updated

CVE-2026-90263: Linux kernel · btrfs: check if root is readonly when setting posix acl

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in dc3a6e90a0a6350a6d43fed9f005f54171809580 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in dc3a6e90a0a6350a6d43fed9f005f54171809580, d5602f96ff1e266f069b4d0d94f441050e057e06, ce8103676f4d4b13e1f087fcfb34f80774d30be2 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 353c2ea735e4b54fb6250861e67b51b1bcb47198, < dc3a6e90a0a6350a6d43fed9f005f54171809580
Fixed in
  • dc3a6e90a0a6350a6d43fed9f005f54171809580
LinuxLinuxAffected
  • ≥ 353c2ea735e4b54fb6250861e67b51b1bcb47198, < d5602f96ff1e266f069b4d0d94f441050e057e06
Fixed in
  • d5602f96ff1e266f069b4d0d94f441050e057e06
LinuxLinuxAffected
  • ≥ 353c2ea735e4b54fb6250861e67b51b1bcb47198, < ce8103676f4d4b13e1f087fcfb34f80774d30be2
Fixed in
  • ce8103676f4d4b13e1f087fcfb34f80774d30be2
LinuxLinuxAffected
  • ≥ 353c2ea735e4b54fb6250861e67b51b1bcb47198, < 20b2c2f3316e82a76ae3358c0bd45824f50f3fd5
Fixed in
  • 20b2c2f3316e82a76ae3358c0bd45824f50f3fd5
LinuxLinuxAffected
  • ≥ 353c2ea735e4b54fb6250861e67b51b1bcb47198, < 01c2f41fc441f75b3f9326443372faceb1cb6638
Fixed in
  • 01c2f41fc441f75b3f9326443372faceb1cb6638
LinuxLinuxAffected
  • =5.2
Fixed in–

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.

References

Community reviews

Loading reviews…