CVE-2026-31600

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. A secondary CVSS source baseline 7.5; sources differ by 0.0.

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

Also known asEUVD-2026-25493 (ENISA EUVD) · GHSA-6447-4w47-gh9g (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.476896] Unable to handle kernel paging request at virtual address ffff000019600000 [ 15.513762] Mem abort info: [ 15.527245] ESR = 0x0000000096000046 [ 15.548553] EC = 0x25: DABT (current EL), IL = 32 bits [ 15.572146] SET = 0, FnV = 0 [ 15.592141] EA = 0, S1PTW = 0 [ 15.612694] FSC = 0x06: level 2 translation fault [ 15.640644] Data abort info: [ 15.661983] ISV = 0, ISS = 0x00000046, ISS2 = 0x00000000 [ 15.694875] CM = 0, WnR = 1, TnD = 0, TagAccess = 0 [ 15.723740] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 15.755776] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000081f3f000 [ 15.800410] [ffff000019600000] pgd=0000000000000000, p4d=180000009ffff403, pud=180000009fffe403, pmd=00e8000199600704 [ 15.855046] Internal error: Oops: 0000000096000046 [#1] SMP [ 15.886394] Modules linked in: [ 15.900029] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc4-dirty #4 PREEMPT [ 15.935258] Hardware name: linux,dummy-virt (DT) [ 15.955612] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) [ 15.986009] pc : __pi_memcpy_generic+0x128/0x22c [ 16.006163] lr : swiotlb_bounce+0xf4/0x158 [ 16.024145] sp : ffff80008000b8f0 [ 16.038896] x29: ffff80008000b8f0 x28: 0000000000000000 x27: 0000000000000000 [ 16.069953] x26: ffffb3976d261ba8 x25: 0000000000000000 x24: ffff000019600000 [ 16.100876] x23: 0000000000000001 x22: ffff0000043430d0 x21: 0000000000007ff0 [ 16.131946] x20: 0000000084570010 x19: 0000000000000000 x18: ffff00001ffe3fcc [ 16.163073] x17: 0000000000000000 x16: 00000000003fffff x15: 646e612065766974 [ 16.194131] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 16.225059] x11: 0000000000000000 x10: 0000000000000010 x9 : 0000000000000018 [ 16.256113] x8 : 0000000000000018 x7 : 0000000000000000 x6 : 0000000000000000 [ 16.287203] x5 : ffff000019607ff0 x4 : ffff000004578000 x3 : ffff000019600000 [ 16.318145] x2 : 0000000000007ff0 x1 : ffff000004570010 x0 : ffff000019600000 [ 16.349071] Call trace: [ 16.360143] __pi_memcpy_generic+0x128/0x22c (P) [ 16.380310] swiotlb_tbl_map_single+0x154/0x2b4 [ 16.400282] swiotlb_map+0x5c/0x228 [ 16.415984] dma_map_phys+0x244/0x2b8 [ 16.432199] dma_map_page_attrs+0x44/0x58 [ 16.449782] virtqueue_map_page_attrs+0x38/0x44 [ 16.469596] virtqueue_map_single_attrs+0xc0/0x130 [ 16.490509] virtnet_rq_alloc.isra.0+0xa4/0x1fc [ 16.510355] try_fill_recv+0x2a4/0x584 [ 16.526989] virtnet_open+0xd4/0x238 [ 16.542775] __dev_open+0x110/0x24c [ 16.558280] __dev_change_flags+0x194/0x20c [ 16.576879] netif_change_flags+0x24/0x6c [ 16.594489] dev_change_flags+0x48/0x7c [ 16.611462] ip_auto_config+0x258/0x1114 [ 16.628727] do_one_initcall+0x80/0x1c8 [ 16.645590] kernel_init_freeable+0x208/0x2f0 [ 16.664917] kernel_init+0x24/0x1e0 [ 16.680295] ret_from_fork+0x10/0x20 [ 16.696369] Code: 927cec03 cb0e0021 8b0e0042 a9411c26 (a900340c) [ 16.723106] ---[ end trace 0000000000000000 ]--- [ 16.752866] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 16.792556] Kernel Offset: 0x3396ea200000 from 0xffff8000800000 ---truncated---

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
21st
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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 24, 2026

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Apr 29, 2026
Patch available.
Web page

arm64: mm: Handle invalid large leaf mappings correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

arm64: mm: Handle invalid large leaf mappings correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8140b21d19015227a28c255404462f2d3e6edc9a
Web page

arm64: mm: Handle invalid large leaf mappings correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/747b6482e4e227fd351197dde6f64a97107a9e52
Web page

arm64: mm: Handle invalid large leaf mappings correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15bfba1ad77fad8e45a37aae54b3c813b33fe27c

Vendor Advisories for CVE-2026-31600(1)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-10-27ubuntu
linuxKernel @ 6.18.24 (fixes >=6.18.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

(1 across 1 ecosystem)
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.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 50× 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 332 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 237 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31600?
CVE-2026-31600 is a high-severity vulnerability; its CVE record was published on April 24, 2026. 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…
When was the CVE record for CVE-2026-31600 published?
The CVE record for CVE-2026-31600 was published on April 24, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-31600 actively exploited?
CVE-2026-31600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31600?
CVE-2026-31600 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-31600?
A fix for CVE-2026-31600 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31600 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-31600

Explore →

Is Your Infrastructure Affected by CVE-2026-31600?

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

Book a Demo →Browse All CVEs