Skip to main content

Linux CVE-2026-23346

| EUVDEUVD-2026-15313 MEDIUM
2026-03-25 Linux GHSA-xqp7-9gqv-6978
5.5
CVSS 3.1 · NVD
View

Vulnerability Assessment

Impact

While CVSS and EPSS scores are unavailable in the intelligence data, the practical risk is elevated on ARM64 systems with PAN enabled (modern security configurations). The vulnerability requires local access and involves reading kernel or mapped physical memory, indicating moderate attack complexity. The patch references from stable kernel repositories (commits 3d64dcc0799c2d6921ba027716b7be721eb19fa8, d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a, 8f098037139b294050053123ab2bc0f819d08932) demonstrate this is a confirmed issue with available fixes. The Information Disclosure tag confirms the primary impact. The fact that generic_access_phys() is invoked through standard operations like reading /proc/[pid]/environ shows the attack surface is accessible to unprivileged local users without requiring special exploitation techniques or POC development.

Exploit ScenarioDerived

A local unprivileged user on an ARM64 system reads /proc/[pid]/environ to access environment variables from a privileged process or access sensitive kernel memory. Due to the ioremap_prot() vulnerability, the kernel's attempt to access the physical pages backing the target process's memory succeeds despite PAN protections by using user-space page attributes, allowing the generic_access_phys() code path to read kernel memory that should be protected. This information disclosure attack requires only file-read access to procfs and standard C library calls, making it trivially exploitable on vulnerable systems without requiring privilege escalation or custom exploitation code.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

A memory access protection bypass vulnerability exists in the Linux kernel's ARM64 ioremap_prot() function where user-space page protection attributes are improperly propagated to kernel-space I/O remapping, bypassing Privileged Access Never (PAN) protections and enabling information disclosure. This affects all Linux kernel versions on ARM64 systems with PAN enabled. An attacker with local access can trigger memory access faults and potentially read sensitive kernel memory through operations like accessing /proc/[pid]/environ on vulnerable systems.

RemediationAI

Update the Linux kernel to a version incorporating the security patches referenced in the stable kernel repository (commits 3d64dcc0799c2d6921ba027716b7be721eb19fa8, d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a, or 8f098037139b294050053123ab2bc0f819d08932). Most distributions have backported these fixes into stable release branches: RHEL should apply the latest kernel-core update, Ubuntu users should install the latest linux-image package for their kernel series, and Debian users should upgrade to the latest stable kernel. Until patching is possible, restrict local user access on ARM64 systems through privilege separation and disable unnecessary access to /proc/[pid]/ file contents via securityfs restrictions or AppArmor/SELinux profiles. Verify PAN is enabled in your kernel configuration (CONFIG_ARM64_PAN) and ensure you are running an updated, patched kernel version.

Affected VersionsENISA

Linux patch: 7.0-rc2
Linux patch: 6.19.7
Linux patch: 0
Linux 893dea9ccd08dab924839354aba21d4ed7a9abc0 <3d64dcc0799c2d6921ba027716b7be721eb19fa8
Linux 893dea9ccd08dab924839354aba21d4ed7a9abc0 <8f098037139b294050053123ab2bc0f819d08932
Linux 893dea9ccd08dab924839354aba21d4ed7a9abc0 <d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a
Linux 6.0
Linux patch: 6.18.17

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the ARM64 architecture-specific I/O memory remapping implementation within the Linux kernel (affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*). The root cause involves improper handling of page table entry (pte) attributes in ioremap_prot(), which is called by generic_access_phys() when the kernel needs to access physical memory via user-space virtual address mappings. On ARM64, the pgprot_t structure contains permission control bits intended for user-space access, and when these are directly used for kernel I/O remapping, they create kernel-accessible mappings with user-space permission restrictions. This violates the ARM64 PAN protection mechanism, which enforces kernel code cannot directly access user memory. The vulnerability class relates to improper permission/attribute handling during memory mapping transitions between user and kernel contexts.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
Apr 24, 2026 - 18:22 NVD
5.5 (MEDIUM)
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Mar 25, 2026 - 10:27 nvd
N/A

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

arm64: io: Extract user memory type in ioremap_prot()

The only caller of ioremap_prot() outside of the generic ioremap() implementation is generic_access_phys(), which passes a 'pgprot_t' value determined from the user mapping of the target 'pfn' being accessed by the kernel. On arm64, the 'pgprot_t' contains all of the non-address bits from the pte, including the permission controls, and so we end up returning a new user mapping from ioremap_prot() which faults when accessed from the kernel on systems with PAN:

| Unable to handle kernel read from unreadable memory at virtual address ffff80008ea89000 | ... | Call trace: | __memcpy_fromio+0x80/0xf8 | generic_access_phys+0x20c/0x2b8 | __access_remote_vm+0x46c/0x5b8 | access_remote_vm+0x18/0x30 | environ_read+0x238/0x3e8 | vfs_read+0xe4/0x2b0 | ksys_read+0xcc/0x178 | __arm64_sys_read+0x4c/0x68 Extract only the memory type from the user 'pgprot_t' in ioremap_prot() and assert that we're being passed a user mapping, to protect us against any changes in future that may require additional handling. To avoid falsely flagging users of ioremap(), provide our own ioremap() macro which simply wraps __ioremap_prot().

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Linux Kernel Multiple Vulnerabilities

View all 4

Vendor StatusVendor

Debian

linux
Release Status Fixed Version Urgency
bullseye not-affected - -
bullseye (security) fixed 5.10.251-1 -
bookworm vulnerable 6.1.159-1 -
bookworm (security) vulnerable 6.1.164-1 -
trixie vulnerable 6.12.73-1 -
trixie (security) vulnerable 6.12.74-2 -
forky, sid fixed 6.19.8-1 -
(unstable) fixed 6.19.8-1 -

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy