CVE-2026-31686

HIGHCVSS · not yet scored7.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-27.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2026-25882 (ENISA EUVD) · GHSA-p63m-cmvw-gf7r (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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:phyp pSeries Call Trace: dump_stack_lvl+0x88/0xc4 (unreliable) print_report+0x214/0x63c kasan_report_invalid_free+0xe4/0x110 check_slab_allocation+0x100/0x150 kmem_cache_free+0x128/0x6e0 kasan_remove_zero_shadow+0x9c4/0xa20 memunmap_pages+0x2b8/0x5c0 devm_action_release+0x54/0x70 release_nodes+0xc8/0x1a0 devres_release_all+0xe0/0x140 device_unbind_cleanup+0x30/0x120 device_release_driver_internal+0x3e4/0x450 unbind_store+0xfc/0x110 drv_attr_store+0x78/0xb0 sysfs_kf_write+0x114/0x140 kernfs_fop_write_iter+0x264/0x3f0 vfs_write+0x3bc/0x7d0 ksys_write+0xa4/0x190 system_call_exception+0x190/0x480 system_call_vectored_common+0x15c/0x2ec ---- interrupt: 3000 at 0x7fff93b3d3f4 NIP: 00007fff93b3d3f4 LR: 00007fff93b3d3f4 CTR: 0000000000000000 REGS: c0000003f1b07e80 TRAP: 3000 Not tainted (6.19.0-rc1-00048-gea1013c15392) MSR: 800000000280f033 CR: 48888208 XER: 00000000 <...> NIP [00007fff93b3d3f4] 0x7fff93b3d3f4 LR [00007fff93b3d3f4] 0x7fff93b3d3f4 ---- interrupt: 3000

The buggy address belongs to the object at c0000003c38e0000 which belongs to the cache pgtable-2^9 of size 4096 The buggy address is located 0 bytes inside of 4096-byte region [c0000003c38e0000, c0000003c38e1000)

The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x3c38c head: order:2 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 memcg:c0000003bfd63e01 flags: 0x63ffff800000040(head|node=6|zone=0|lastcpupid=0x7ffff) page_type: f5(slab) raw: 063ffff800000040 c000000140058980 5deadbeef0000122 0000000000000000 raw: 0000000000000000 0000000080200020 00000000f5000000 c0000003bfd63e01 head: 063ffff800000040 c000000140058980 5deadbeef0000122 0000000000000000 head: 0000000000000000 0000000080200020 00000000f5000000 c0000003bfd63e01 head: 063ffff800000002 c00c000000f0e301 00000000ffffffff 00000000ffffffff head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000004 page dumped because: kasan: bad access detected

[ 138.953636] [ T2164] Memory state around the buggy address: [ 138.953643] [ T2164] c0000003c38dff00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 138.953652] [ T2164] c0000003c38dff80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 138.953661] [ T2164] >c0000003c38e0000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 138.953669] [ T2164] ^ [ 138.953675] [ T2164] c0000003c38e0080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 138.953684] [ T2164] c0000003c38e0100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 138.953692] [ T2164] ================================================================== [ 138.953701] [ T2164] Disabling lock debugging due to kernel taint

CVSS v3
—
EG Score
7.8HIGHlow confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 27, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated May 6, 2026
Patch available.
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f6204f7ff6aff62ce6242a76982c5ba3a9ded707
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cec74b2ab7dff866b1d77eaa545b9e8fd14a1f87
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b38237a2ea9c6c19836eee2c57037e1f9f103576
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a05f77cb227c39c5069aea6f12762a29d1e6c103
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85d98614e089a67dc6faa8ca766fe10a639f82b4
Web page

mm/kasan: fix double free for kasan pXds - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51d8c78be0c27ddb91bc2c0263941d8b30a47d3b

Vendor Advisories for CVE-2026-31686(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-10-24ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-24ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-24ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-24ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-24ubuntu
linuxKernel @ 5.10.258 (fixes >=4.19.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (130 versions)
  • every version up to 6.19.14-1: fixed in 6.19.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 269 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 174 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-25 14:36 UTCEG score recompute
  7. 2026-10-24 23:02 UTCEG score recompute
  8. 2026-10-24 23:02 UTCVendor advisory
  9. 2026-10-24 23:01 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-18 03:48 UTCEG score recompute
  18. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-17 15:59 UTCEG score recompute
  20. 2026-10-17 15:58 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-13 17:24 UTCOSV refresh
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 70 more
  1. 2026-10-12 16:15 UTCEG score recompute
  2. 2026-10-11 19:57 UTCEG score recompute
  3. 2026-10-11 17:10 UTCEG score recompute
  4. 2026-10-11 14:39 UTCEG score recompute
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-23 07:15 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-04 01:46 UTCOSV refresh
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-08-17 14:02 UTCEG score recompute
  46. 2026-08-17 14:02 UTCVendor advisory
  47. 2026-08-17 14:02 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-08-16 05:37 UTCEG score recompute
  51. 2026-08-16 05:37 UTCVendor advisory
  52. 2026-08-16 05:37 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-08-14 17:01 UTCVendor advisory
  56. 2026-08-14 17:01 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-08-14 04:01 UTCEG score recompute
  58. 2026-08-14 04:01 UTCVendor advisory
  59. 2026-08-14 04:01 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-08-13 08:26 UTCVendor advisory
  62. 2026-08-13 08:26 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-08-12 17:41 UTCEG score recompute
  64. 2026-08-12 17:41 UTCVendor advisory
  65. 2026-08-12 17:41 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-08-11 16:39 UTCEG score recompute
  68. 2026-08-11 16:39 UTCVendor advisory
  69. 2026-08-11 16:39 UTCGHSA enrichmentGHSA-p63m-cmvw-gf7r · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-11 02:01 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-31686?
CVE-2026-31686 is a high-severity vulnerability; its CVE record was published on April 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/kasan: fix double free for kasan pXds kasanfreepxd() 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)…
When was the CVE record for CVE-2026-31686 published?
The CVE record for CVE-2026-31686 was published on April 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 14, 2026; the record at its source may have been updated since.
Is CVE-2026-31686 actively exploited?
CVE-2026-31686 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-31686?
A fix for CVE-2026-31686 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31686 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31686

Explore →

Is Your Infrastructure Affected by CVE-2026-31686?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs