CVE-2026-46171

NONECVSS 0.0

0.0

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: 0.0(none)
EPSS: 4.3%
KEV: Not listed

Published

May 28, 2026

Last Modified

May 28, 2026

References (3)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1d57ab45ec5c0e22789de793bcf2a31ad6fb7d98
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b7c958d7c1eb1cb9b2be7b5ee4129fcd66cec978
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/bd62c0f61bc722a097417401030c596cea8e21aa

Vendor Advisories for CVE-2026-46171(1)

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

GHSA-wxj9-x4vw-8w2j
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: riscv: kvm: fix vector...

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 10:11 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-46171?

CVE-2026-46171 is a none 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. 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 4.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

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

CVE-2026-46171

📅 Published

🔄 Last Modified

🔗 References (3)

📣 Vendor Advisories for CVE-2026-46171(1)