CVE-2026-31600

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

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

https://git.kernel.org/stable/c/cbea627ea634f41c79d18f0c6d20db66fa93514c
generic

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

https://git.kernel.org/stable/c/8140b21d19015227a28c255404462f2d3e6edc9a
generic

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

https://git.kernel.org/stable/c/747b6482e4e227fd351197dde6f64a97107a9e52
generic

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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.24—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 rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)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 5× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 275 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-04 03:16 UTCOSV refresh
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 14:51 UTCEG score recompute
  4. 2026-08-17 14:51 UTCVendor advisory
  5. 2026-08-17 14:51 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 05:47 UTCEG score recompute
  9. 2026-08-16 05:47 UTCVendor advisory
  10. 2026-08-16 05:47 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 02:00 UTCEG score recompute
  13. 2026-08-15 02:00 UTCVendor advisory
  14. 2026-08-15 02:00 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 15:04 UTCVendor advisory
  17. 2026-08-14 15:04 UTCGHSA enrichment
  18. 2026-08-14 04:08 UTCEG score recompute
  19. 2026-08-14 04:08 UTCVendor advisory
  20. 2026-08-14 04:08 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 04:46 UTCVendor advisory
  23. 2026-08-13 04:46 UTCGHSA enrichment
  24. 2026-08-12 17:50 UTCEG score recompute
  25. 2026-08-12 17:50 UTCVendor advisory
  26. 2026-08-12 17:50 UTCGHSA enrichment
  27. 2026-08-12 13:50 UTCEPSS rescore
  28. 2026-08-11 16:41 UTCEG score recompute
  29. 2026-08-11 16:41 UTCVendor advisory
  30. 2026-08-11 16:41 UTCGHSA enrichment
  31. 2026-08-11 02:09 UTCEG score recompute
  32. 2026-08-11 02:09 UTCVendor advisory
  33. 2026-08-11 02:09 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 12:10 UTCVendor advisory
  36. 2026-08-10 12:10 UTCGHSA enrichment
  37. 2026-08-10 01:12 UTCVendor advisory
  38. 2026-08-10 01:12 UTCGHSA enrichment
  39. 2026-08-09 14:16 UTCEG score recompute
  40. 2026-08-09 14:16 UTCVendor advisory
  41. 2026-08-09 14:16 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 03:19 UTCEG score recompute
  44. 2026-08-09 03:19 UTCVendor advisory
  45. 2026-08-09 03:19 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 10:27 UTCVendor advisory
  48. 2026-08-08 10:27 UTCGHSA enrichment
  49. 2026-08-07 23:31 UTCEG score recompute
  50. 2026-08-07 23:31 UTCVendor advisory
  51. 2026-08-07 23:31 UTCGHSA enrichment
  52. 2026-08-07 12:36 UTCVendor advisory
  53. 2026-08-07 12:36 UTCGHSA enrichment
  54. 2026-08-06 21:25 UTCEG score recompute
  55. 2026-08-06 21:25 UTCVendor advisory
  56. 2026-08-06 21:25 UTCGHSA enrichment
  57. 2026-08-06 13:46 UTCEPSS rescore
  58. 2026-08-06 10:29 UTCVendor advisory
  59. 2026-08-06 10:29 UTCGHSA enrichment
  60. 2026-08-05 23:34 UTCEG score recompute
  61. 2026-08-05 23:34 UTCVendor advisory
  62. 2026-08-05 23:34 UTCGHSA enrichment
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 12:38 UTCEG score recompute
  65. 2026-08-05 12:38 UTCVendor advisory
  66. 2026-08-05 12:38 UTCGHSA enrichment
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:38 UTCEPSS rescore
  69. 2026-08-03 21:03 UTCVendor advisory
  70. 2026-08-03 21:03 UTCGHSA enrichment
  71. 2026-08-02 22:18 UTCVendor advisory
  72. 2026-08-02 22:18 UTCGHSA enrichment
  73. 2026-08-02 11:21 UTCEG score recompute
  74. 2026-08-02 11:21 UTCVendor advisory
  75. 2026-08-02 11:21 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-31600?
CVE-2026-31600 is a high vulnerability 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 CVE-2026-31600 disclosed?
CVE-2026-31600 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31600 actively exploited?
CVE-2026-31600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31600?
CVE-2026-31600 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31600, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs