CVE-2026-31558

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: 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:

LoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust

kvm_get_vcpu_by_cpuid() takes a cpuid parameter whose type is int, so cpuid can be negative. Let kvm_get_vcpu_by_cpuid() return NULL for this case so as to make it more robust.

This fix an out-of-bounds access to kvm_arch::phyid_map::phys_map[].

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

LoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/878cf6acb4fd8ab4126cf9d369a5bb0e23123418
generic

LoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/596c3f8069c4792f22fce8c4452f44410032d910
generic

LoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47857b05bd50db01e211a1b6f513d57901cd3e6b
generic

LoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2db06c15d8c7a0ccb6108524e16cd9163753f354

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.80—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-31558?
CVE-2026-31558 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Make kvmgetvcpubycpuid() more robust kvmgetvcpubycpuid() takes a cpuid parameter whose type is int, so cpuid can be negative. Let kvmgetvcpubycpuid() return NULL for this case so as to make it more robust. This fix…
When was CVE-2026-31558 disclosed?
CVE-2026-31558 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-31558 actively exploited?
CVE-2026-31558 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31558?
CVE-2026-31558 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31558?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31558, 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-31558

Explore →

Is Your Infrastructure Affected by CVE-2026-31558?

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

Start Free Scan →Browse All CVEs