CVE-2026-31588

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week
8.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.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

KVM: x86: Use scratch field in MMIO fragment to hold small write values

When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data payload is 8 bytes or less, i.e. can fit in a single chunk, instead of pointing the fragment directly at the source value.

This fixes a class of use-after-free bugs that occur when the emulator initiates a write using an on-stack, local variable as the source, the write splits a page boundary, *and* both pages are MMIO pages. Because KVM's ABI only allows for physically contiguous MMIO requests, accesses that split MMIO pages are separated into two fragments, and are sent to userspace one at a time. When KVM attempts to complete userspace MMIO in response to KVM_RUN after the first fragment, KVM will detect the second fragment and generate a second userspace exit, and reference the on-stack variable.

The issue is most visible if the second KVM_RUN is performed by a separate task, in which case the stack of the initiating task can show up as truly freed data.

================================================================== BUG: KASAN: use-after-free in complete_emulated_mmio+0x305/0x420 Read of size 1 at addr ffff888009c378d1 by task syz-executor417/984

CPU: 1 PID: 984 Comm: syz-executor417 Not tainted 5.10.0-182.0.0.95.h2627.eulerosv2r13.x86_64 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack+0xbe/0xfd print_address_description.constprop.0+0x19/0x170 __kasan_report.cold+0x6c/0x84 kasan_report+0x3a/0x50 check_memory_region+0xfd/0x1f0 memcpy+0x20/0x60 complete_emulated_mmio+0x305/0x420 kvm_arch_vcpu_ioctl_run+0x63f/0x6d0 kvm_vcpu_ioctl+0x413/0xb20 __se_sys_ioctl+0x111/0x160 do_syscall_64+0x30/0x40 entry_SYSCALL_64_after_hwframe+0x67/0xd1 RIP: 0033:0x42477d Code: <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007faa8e6890e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00000000004d7338 RCX: 000000000042477d RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005 RBP: 00000000004d7330 R08: 00007fff28d546df R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004d733c R13: 0000000000000000 R14: 000000000040a200 R15: 00007fff28d54720

The buggy address belongs to the page: page:0000000029f6a428 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x9c37 flags: 0xfffffc0000000(node=0|zone=1|lastcpupid=0x1fffff) raw: 000fffffc0000000 0000000000000000 ffffea0000270dc8 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888009c37780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888009c37800: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888009c37880: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888009c37900: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888009c37980: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================

The bug can also be reproduced with a targeted KVM-Unit-Test by hacking KVM to fill a large on-stack variable in complete_emulated_mmio(), i.e. by overwrite the data value with garbage.

Limit the use of the scratch fields to 8-byte or smaller accesses, and to just writes, as larger accesses and reads are not affected thanks to implementation details in the emulator, but add a sanity check to ensure those details don't change in the future. Specifically, KVM never uses on-stack variables for accesses larger that 8 bytes, e.g. uses an operand in the emulator context, and *al ---truncated---

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.2%
EPSS %ILE
8th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 (6)

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

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a7b6d75c8f85b09dea893f64a85a356bcf6c3fe
Web page

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b83d91e9ae92fe1258d7040a32430bbb3bb7d6e
Web page

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22d2ff69d487a32a8b88f9c970120fc2daa08a77
Web page

KVM: x86: Use scratch field in MMIO fragment to hold small write values - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b16e69d17d8c35c5c9d5918bf596c75a44655d3

Vendor Advisories for CVE-2026-31588(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-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1112.119~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-19ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-19ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-19ubuntu
linuxKernel @ 5.10.258 (fixes >=3.5.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.

Additional Vendor Advisories

(24)

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 21× in last 7d / 42× 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 294 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 199 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31588?
CVE-2026-31588 is a high-severity vulnerability; its CVE record was published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use scratch field in MMIO fragment to hold small write values When exiting to userspace to service an emulated MMIO write, copy the to-be-written value to a scratch field in the MMIO fragment if the size of the data…
When was the CVE record for CVE-2026-31588 published?
The CVE record for CVE-2026-31588 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-31588 actively exploited?
CVE-2026-31588 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31588?
CVE-2026-31588 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-31588?
A fix for CVE-2026-31588 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31588 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-31588

Explore →

Is Your Infrastructure Affected by CVE-2026-31588?

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

Book a Demo →Browse All CVEs