LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50232: arm64: set UXN on swapper page tables

In the Linux kernel, the following vulnerability has been resolved: arm64: set UXN on swapper page tables [ This issue was fixed upstream by accident in c3cee924bd85 ("arm64: head: cover entire kernel image in initial ID map") as part of a large refactoring of the arm64 boot flow. This simple fix is therefore preferred for -stable backporting ] On a system that implements FEAT_EPAN, read/write access to the idmap is denied because UXN is not set on the swapper PTEs. As a result, idmap_kpti_install_ng_mappings panics the kernel when accessing __idmap_kpti_flag. Fix it by setting UXN on these PTEs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50232 is a Linux kernel arm64 issue that can cause a kernel panic on systems with the FEAT_EPAN CPU feature. The available sources describe an availability problem, not data theft or remote code execution. No active exploitation is reported in the provided sources or KEV status.

Executive priority

Prioritize for arm64 Linux fleets where unplanned downtime is costly. This is not evidenced as an internet-exploited emergency, but kernel panics can affect service availability. Patch through normal kernel maintenance unless affected systems are business-critical or already showing related crashes.

Technical view

On arm64, swapper page-table entries lacked UXN. On systems implementing FEAT_EPAN, read/write access to the idmap was denied, causing idmap_kpti_install_ng_mappings to panic when accessing __idmap_kpti_flag. Upstream indicates the issue was fixed by setting UXN, with an earlier refactor also accidentally resolving it.

Likely exposure

Exposure appears limited to Linux arm64 systems running affected kernel versions and hardware implementing FEAT_EPAN. The source data indicates fixes around stable commit 775871d4 and upstream commit c3cee924, with version markers including 5.13, 5.15.60, and 6.0.

Exploitation context

The sources describe a kernel panic condition tied to kernel memory mapping behavior on specific arm64 systems. They do not document remote exploitation, privilege escalation, public exploit activity, or CISA KEV listing. Treat this primarily as a stability and availability risk.

Researcher notes

Evidence is limited to kernel CVE text and git references. No CVSS, CWE, exploit status, or distro-specific package list is provided. Analysis should focus on commit presence, arm64 configuration, FEAT_EPAN support, and whether vendor kernels already backported the fix.

Mitigation direction

  • Identify arm64 Linux systems with affected kernel versions and FEAT_EPAN-capable CPUs.
  • Update to a vendor kernel containing the referenced stable fix.
  • If using custom kernels, verify inclusion of commit 775871d4 or equivalent UXN change.
  • Monitor distribution advisories for backported fixes and reboot requirements.

Validation and detection

  • Check deployed kernel versions against vendor advisories and the referenced stable commits.
  • Confirm whether production arm64 hardware implements FEAT_EPAN.
  • Review kernel build or source history for the UXN swapper PTE fix.
  • After patching, validate normal boot and KPTI-related behavior on representative systems.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50232 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux18107f8a2df6bf1c6cac8d0713f757f866d5af51, 18107f8a2df6bf1c6cac8d0713f757f866d5af51unaffected
LinuxLinux5.13, 0, 5.15.60, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.