{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90263 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90263 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90263 and fix it if it is affected.\n\nWhat it is: CVE-2026-90263 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90263 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90263/ (Markdown: https://insights.sbomify.com/CVE-2026-90263/index.md)","id":"CVE-2026-90263","markdown":"https://insights.sbomify.com/CVE-2026-90263/index.md","name":"CVE-2026-90263","record":{"aliases":["AZL-102465","BELL-CVE-2026-90263","DEBIAN-CVE-2026-90263","GHSA-wxw8-hpqh-3xg2","UBUNTU-CVE-2026-90263"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel filesystem","requires_auth":"low_privilege","summary":"Attackers can modify POSIX ACLs on read-only Btrfs filesystems, bypassing intended write restrictions and altering file permissions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: check if root is readonly when setting posix acl\n\nFor a filesystem which has btrfs read-only property set to true, all\nwrite operations including acl and xattr should be denied. However, acl\ncan still be set even if btrfs ro property is true.\n\nThis happens because no function on the set_acl code path checks the root\nis readonly or not. It was checked in btrfs_setxattr_trans() but got\nremoved in commit 353c2ea735e4 (\"btrfs: remove redundant readonly root\ncheck in btrfs_setxattr_trans\")\n\nThat commit didn't check if all the callers properly check the root's\nread-only flag. A previous fix is commit b51111271b03 (\"btrfs: check if\nroot is readonly while setting security xattr\").\n\nAlways check if the root is read-only before performing the set acl\noperation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"btrfs: check if root is readonly when setting posix acl","id":"CVE-2026-90263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"btrfs: always wait for ordered extents to avoid OE races","id":"CVE-2026-90264"},"packages":[],"prev":{"headline":"btrfs: retry verity reads for not-uptodate Merkle folios","id":"CVE-2026-90262"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"Attackers can modify POSIX ACLs on read-only Btrfs filesystems, bypassing intended write restrictions and altering file permissions.","url":"https://insights.sbomify.com/CVE-2026-90263/"}