Improper Access Control Affecting kernel6.12-tools-debuginfo package, versions <1:6.12.114-139.210.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.21% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNEL612TOOLSDEBUGINFO-22395434
  • published10 Nov 2026
  • disclosed17 Sept 2026

Introduced: 17 Sep 2026

CVE-2026-90263  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel6.12-tools-debuginfo to version 1:6.12.114-139.210.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3402.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel6.12-tools-debuginfo package and not the kernel6.12-tools-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1