CVE-2026-46171

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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

riscv: kvm: fix vector context allocation leak

When the second kzalloc (host_context.vector.datap) fails in kvm_riscv_vcpu_alloc_vector_context, the first allocation (guest_context.vector.datap) is leaked. Free it before returning.

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

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (3)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

riscv: kvm: fix vector context allocation leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

riscv: kvm: fix vector context allocation leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

riscv: kvm: fix vector context allocation leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d57ab45ec5c0e22789de793bcf2a31ad6fb7d98

Vendor Advisories for CVE-2026-46171(2)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

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.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 63× 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 193 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-46171?
CVE-2026-46171 is a medium vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: riscv: kvm: fix vector context allocation leak When the second kzalloc (host_context.vector.datap) fails in kvmriscvvcpuallocvector_context, the first allocation (guest_context.vector.datap) is leaked. Free it before returning.
When was CVE-2026-46171 disclosed?
CVE-2026-46171 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46171 actively exploited?
CVE-2026-46171 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.4% of all scored CVEs.
How do I remediate CVE-2026-46171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46171, 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-46171

Explore →

Is Your Infrastructure Affected by CVE-2026-46171?

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

Start Free Scan →Browse All CVEs