CVE-2026-31592

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-25485 (ENISA EUVD) · GHSA-p3hp-qchj-85wc (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock

Take and hold kvm->lock for before checking sev_guest() in sev_mem_enc_register_region(), as sev_guest() isn't stable unless kvm->lock is held (or KVM can guarantee KVM_SEV_INIT{2} has completed and can't rollack state). If KVM_SEV_INIT{2} fails, KVM can end up trying to add to a not-yet-initialized sev->regions_list, e.g. triggering a #GP

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 110 UID: 0 PID: 72717 Comm: syz.15.11462 Tainted: G U W O 6.16.0-smp-DEV #1 NONE Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024 RIP: 0010:sev_mem_enc_register_region+0x3f0/0x4f0 ../include/linux/list.h:83 Code: <41> 80 3c 04 00 74 08 4c 89 ff e8 f1 c7 a2 00 49 39 ed 0f 84 c6 00 RSP: 0018:ffff88838647fbb8 EFLAGS: 00010256 RAX: dffffc0000000000 RBX: 1ffff92015cf1e0b RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff888367870000 RBP: ffffc900ae78f050 R08: ffffea000d9e0007 R09: 1ffffd4001b3c000 R10: dffffc0000000000 R11: fffff94001b3c001 R12: 0000000000000000 R13: ffff8982ab0bde00 R14: ffffc900ae78f058 R15: 0000000000000000 FS: 00007f34e9dc66c0(0000) GS:ffff89ee64d33000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe180adef98 CR3: 000000047210e000 CR4: 0000000000350ef0 Call Trace: kvm_arch_vm_ioctl+0xa72/0x1240 ../arch/x86/kvm/x86.c:7371 kvm_vm_ioctl+0x649/0x990 ../virt/kvm/kvm_main.c:5363 __se_sys_ioctl+0x101/0x170 ../fs/ioctl.c:51 do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x6f/0x1f0 ../arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f34e9f7e9a9 Code: <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f34e9dc6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f34ea1a6080 RCX: 00007f34e9f7e9a9 RDX: 0000200000000280 RSI: 000000008010aebb RDI: 0000000000000007 RBP: 00007f34ea000d69 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f34ea1a6080 R15: 00007ffce77197a8

with a syzlang reproducer that looks like:

syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000040)={0x0, &(0x7f0000000180)=ANY=[], 0x70}) (async) syz_kvm_add_vcpu$x86(0x0, &(0x7f0000000080)={0x0, &(0x7f0000000180)=ANY=[@ANYBLOB="..."], 0x4f}) (async) r0 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000200), 0x0, 0x0) r1 = ioctl$KVM_CREATE_VM(r0, 0xae01, 0x0) r2 = openat$kvm(0xffffffffffffff9c, &(0x7f0000000240), 0x0, 0x0) r3 = ioctl$KVM_CREATE_VM(r2, 0xae01, 0x0) ioctl$KVM_SET_CLOCK(r3, 0xc008aeba, &(0x7f0000000040)={0x1, 0x8, 0x0, 0x5625e9b0}) (async) ioctl$KVM_SET_PIT2(r3, 0x8010aebb, &(0x7f0000000280)={[...], 0x5}) (async) ioctl$KVM_SET_PIT2(r1, 0x4070aea0, 0x0) (async) r4 = ioctl$KVM_CREATE_VM(0xffffffffffffffff, 0xae01, 0x0) openat$kvm(0xffffffffffffff9c, 0x0, 0x0, 0x0) (async) ioctl$KVM_SET_USER_MEMORY_REGION(r4, 0x4020ae46, &(0x7f0000000400)={0x0, 0x0, 0x0, 0x2000, &(0x7f0000001000/0x2000)=nil}) (async) r5 = ioctl$KVM_CREATE_VCPU(r4, 0xae41, 0x2) close(r0) (async) openat$kvm(0xffffffffffffff9c, &(0x7f0000000000), 0x8000, 0x0) (async) ioctl$KVM_SET_GUEST_DEBUG(r5, 0x4048ae9b, &(0x7f0000000300)={0x4376ea830d46549b, 0x0, [0x46, 0x0, 0x0, 0x0, 0x0, 0x1000]}) (async) ioctl$KVM_RUN(r5, 0xae80, 0x0)

Opportunistically use guard() to avoid having to define a new error label and goto usage.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
4th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-11-11). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

November 11, 2026

Advisory Details (6)

Auto-updated Oct 25, 2026
Patch available.
Web page

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/777a8ebd2da3529a455af022ed929408fdbb161f
Web page

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35a0963d361f98bba798fd15d229dcb166c04684
Web page

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25c85d5831201391fb920d51067c6d93cce55348
Web page

KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-31592(2)

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

Patch Availability(7)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (376 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (133 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 8× in last 7d / 46× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 295 rows on record for this CVE, as 96 entries (4 repeats merged).

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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 195 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31592?
CVE-2026-31592 is a medium-severity vulnerability; its CVE record was published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect all of sev_mem_enc_register_region() with kvm->lock Take and hold kvm->lock for before checking sev_guest() in sev_mem_enc_register_region(), as sev_guest() isn't stable unless kvm->lock is held (or KVM can…
When was the CVE record for CVE-2026-31592 published?
The CVE record for CVE-2026-31592 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 November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-31592 actively exploited?
CVE-2026-31592 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31592?
CVE-2026-31592 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31592?
A fix for CVE-2026-31592 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31592 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-31592

Explore →

Is Your Infrastructure Affected by CVE-2026-31592?

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

Book a Demo →Browse All CVEs