Incorrect Execution-Assigned Permissions Affecting kernel6.18-tools-devel package, versions <1:6.18.41-94.142.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.19% (9th 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-KERNEL618TOOLSDEVEL-19467552
  • published1 Sept 2026
  • disclosed15 Aug 2026

Introduced: 15 Aug 2026

NewCVE-2026-72279  (opens in a new tab)
CWE-279  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel6.18-tools-devel to version 1:6.18.41-94.142.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2071.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel6.18-tools-devel package and not the kernel6.18-tools-devel 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:

KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR

KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backing PFN is read-only (e.g. RO memslot), meaning that the L1 VNCR should use at most a read-only mapping.

Cache the writability of the PFN in the VNCR TLB and use it to constrain the resulting fixmap permissions. Promote VNCR permission faults to an SEA in the case where the guest attempts to write to a read-only endpoint. Conveniently, this also plugs a page leak found by Sashiko [*] resulting from the early return for a read-only PFN.

CVSS Base Scores

version 3.1