How to Fix CVE-2026-31600: arm64: mm: Handle invalid large leaf mappings correctly in Linux

By Sai Kiran Pandrala

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-43427: Security Vulnerability in Linux — Security Vulnerability in Linux
• How to Fix CVE-2026-43143: Security Vulnerability in Linux — Security Vulnerability in Linux
• How to Fix CVE-2026-43207: Security Vulnerability in Linux , Security Vulnerability in Linux
• How to Fix CVE-2026-31408: Linux (Bundle Sibling) , Linux (Bundle Sibling)
• How to Fix CVE-2026-31406: Linux (Bundle Sibling) , Linux (Bundle Sibling)

Last verified: 2026-05-25

CVE-2026-31600 is a arm64: mm: handle invalid large leaf mappings correctly in Linux Linux. Fix it by upgrading to 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

What is CVE-2026-31600?

CVE-2026-31600 is a arm64: mm: handle invalid large leaf mappings correctly flaw in Linux Linux. It carries a CVSS base score of 7.5 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: In the Linux kernel, the following vulnerability has been resolved:

arm64: mm: Handle invalid large leaf mappings correctly

It has been possible for a long time to mark ptes in the linear map as

invalid. This is done for secretmem, kfence, realm dma memory un/share,

and others, by simply clearing the PTE_VALID bit. But until commit

a166563e7ec37 ("arm64: mm: support large block mapping when

rodata=full") large leaf mappings were never made invalid in this way.

It turns out various parts of the code base are not equipped to handle

invalid large leaf mappings (in the way they are currently encoded) and

I've observed a kernel panic while booting a realm guest on a

BBML2_NOABORT system as a result:

[ 15.432706] software IO TLB: Memory encryption is active and system is using DMA bounce buffers

[ 15.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31600

Apply the vendor patch. Target the build named in the Fixed in row above (6.18.24, 6.19.14, 7.0.1, 7.1-rc1). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky

sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.

# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31600 being exploited in the wild?

As of 2026-05-25, CVE-2026-31600 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31600?

The CVSS base score is 7.5 (High).

What version fixes this?

Upgrade to 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

• Official vendor advisory: https://git.kernel.org/stable/c/8140b21d19015227a28c255404462f2d3e6edc9a
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31600
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/747b6482e4e227fd351197dde6f64a97107a9e52
• Additional reference: https://git.kernel.org/stable/c/cbea627ea634f41c79d18f0c6d20db66fa93514c
• Additional reference: https://git.kernel.org/stable/c/15bfba1ad77fad8e45a37aae54b3c813b33fe27c

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*