CVE-2026-31601

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24.

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

Also known asEUVD-2026-25494 (ENISA EUVD) · GHSA-v3gv-mm6q-h9jf (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.1%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

vfio/xe: Reorganize the init to decouple migration from reset

Attempting to issue reset on VF devices that don't support migration leads to the following:

BUG: unable to handle page fault for address: 00000000000011f8 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 7443 Comm: xe_sriov_flr Tainted: G S U 7.0.0-rc1-lgci-xe-xe-4588-cec43d5c2696af219-nodebug+ #1 PREEMPT(lazy) Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-P DDR4 RVP, BIOS RPLPFWI1.R00.4035.A00.2301200723 01/20/2023 RIP: 0010:xe_sriov_vfio_wait_flr_done+0xc/0x80 [xe] Code: ff c3 cc cc cc cc 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 41 54 53 <83> bf f8 11 00 00 02 75 61 41 89 f4 85 f6 74 52 48 8b 47 08 48 89 RSP: 0018:ffffc9000f7c39b8 EFLAGS: 00010202 RAX: ffffffffa04d8660 RBX: ffff88813e3e4000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000f7c39c8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff888101a48800 R13: ffff88813e3e4150 R14: ffff888130d0d008 R15: ffff88813e3e40d0 FS: 00007877d3d0d940(0000) GS:ffff88890b6d3000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000011f8 CR3: 000000015a762000 CR4: 0000000000f52ef0 PKRU: 55555554 Call Trace: xe_vfio_pci_reset_done+0x49/0x120 [xe_vfio_pci] pci_dev_restore+0x3b/0x80 pci_reset_function+0x109/0x140 reset_store+0x5c/0xb0 dev_attr_store+0x17/0x40 sysfs_kf_write+0x72/0x90 kernfs_fop_write_iter+0x161/0x1f0 vfs_write+0x261/0x440 ksys_write+0x69/0xf0 __x64_sys_write+0x19/0x30 x64_sys_call+0x259/0x26e0 do_syscall_64+0xcb/0x1500 ? __fput+0x1a2/0x2d0 ? fput_close_sync+0x3d/0xa0 ? __x64_sys_close+0x3e/0x90 ? x64_sys_call+0x1b7c/0x26e0 ? do_syscall_64+0x109/0x1500 ? __task_pid_nr_ns+0x68/0x100 ? __do_sys_getpid+0x1d/0x30 ? x64_sys_call+0x10b5/0x26e0 ? do_syscall_64+0x109/0x1500 ? putname+0x41/0x90 ? do_faccessat+0x1e8/0x300 ? __x64_sys_access+0x1c/0x30 ? x64_sys_call+0x1822/0x26e0 ? do_syscall_64+0x109/0x1500 ? tick_program_event+0x43/0xa0 ? hrtimer_interrupt+0x126/0x260 ? irqentry_exit+0xb2/0x710 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7877d5f1c5a4 Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d a5 ea 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89 RSP: 002b:00007fff48e5f908 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007877d5f1c5a4 RDX: 0000000000000001 RSI: 00007877d621b0c9 RDI: 0000000000000009 RBP: 0000000000000001 R08: 00005fb49113b010 R09: 0000000000000007 R10: 0000000000000000 R11: 0000000000000202 R12: 00007877d621b0c9 R13: 0000000000000009 R14: 00007fff48e5fac0 R15: 00007fff48e5fac0

This is caused by the fact that some of the xe_vfio_pci_core_device members needed for handling reset are only initialized as part of migration init.

Fix the problem by reorganizing the code to decouple VF init from migration init.

CVSS v3
—
EG Score
5.5MEDIUMlow 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
1st
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.1% within 30 daysSource: FIRST EPSS. 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, and whom BOD 26-04 binds: 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 14, 2026

References (3)

Vendor Advisories for CVE-2026-31601(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-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-10-23ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-23ubuntu
linuxKernel @ 6.19.14 (fixes >=6.19.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
—

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

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

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-31601?
CVE-2026-31601 is a medium-severity vulnerability; its CVE record was published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: vfio/xe: Reorganize the init to decouple migration from reset Attempting to issue reset on VF devices that don't support migration leads to the following: BUG: unable to handle page fault for address: 00000000000011f8 #PF:…
When was the CVE record for CVE-2026-31601 published?
The CVE record for CVE-2026-31601 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 June 14, 2026; the record at its source may have been updated since.
Is CVE-2026-31601 actively exploited?
CVE-2026-31601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-31601?
A fix for CVE-2026-31601 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31601 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-31601

Explore →

Is Your Infrastructure Affected by CVE-2026-31601?

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

Book a Demo →Browse All CVEs