Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31686

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: mm/kasan: fix double free for kasan pXds kasan_free_pxd() assumes the page table is always struct page aligned.

Published Apr 27, 2026CWE-415EPSS 0.18%

Overview

CVE-2026-31686 is a high-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

mm/kasan: fix double free for kasan pXds

kasan_free_pxd() assumes the page table is always struct page aligned.

But that's not always the case for all architectures. E.g. In case of

powerpc with 64K pagesize, PUD table (of size 4096) comes from slab cache

named pgtable-2^9. Hence instead of page_to_virt(pxd_page()) let's just

directly pass the start of the pxd table which is passed as the 1st

argument.

This fixes the below double free kasan issue seen with PMEM:

radix-mmu: Mapped 0x0000047d10000000-0x0000047f90000000 with 2.00 MiB pages

==================================================================

BUG: KASAN: double-free in kasan_remove_zero_shadow+0x9c4/0xa20

Free of addr c0000003c38e0000 by task ndctl/2164

CPU: 34 UID: 0 PID: 2164 Comm: ndctl Not tainted 6.19.0-rc1-00048-gea1013c15392 #157 VOLUNTARY

Hardware name: IBM,9080-HEX POWER10 (architected) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_012) hv:phy

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2277246ea265cdca64ce6fdea4b26cd6ff0ec4dbRefgit.kernel.org/stable/c/3298bdf5a878ded06351eb293856fa84e050029eRefgit.kernel.org/stable/c/51d8c78be0c27ddb91bc2c0263941d8b30a47d3bRefgit.kernel.org/stable/c/7d7b2d5c107a1f6302cf0006d859985e7c3ddd1cRefgit.kernel.org/stable/c/85d98614e089a67dc6faa8ca766fe10a639f82b4Refgit.kernel.org/stable/c/a05f77cb227c39c5069aea6f12762a29d1e6c103Refgit.kernel.org/stable/c/b38237a2ea9c6c19836eee2c57037e1f9f103576Refgit.kernel.org/stable/c/cec74b2ab7dff866b1d77eaa545b9e8fd14a1f87Refgit.kernel.org/stable/c/f6204f7ff6aff62ce6242a76982c5ba3a9ded707

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31686?

CVE-2026-31686 is a high-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31686?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31686?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31686?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31686 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999