CVE-2026-46147

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
Trending — 4 sources updated this week
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:

KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()

Two bugs exist in the vCPU initialisation path:

  • If a check fails after hyp_pin_shared_mem() succeeds, the cleanup
path jumps to 'unlock' without calling unpin_host_vcpu() or unpin_host_sve_state(), permanently leaking pin references on the host vCPU and SVE state pages.

Extract a register_hyp_vcpu() helper that performs the checks and the store. When register_hyp_vcpu() returns an error, call unpin_host_vcpu() and unpin_host_sve_state() inline before falling through to the existing 'unlock' label.

  • register_hyp_vcpu() publishes the new vCPU pointer into
'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU object.

Ensure the store uses smp_store_release() and the load uses smp_load_acquire(). While 'vm_table_lock' currently serialises the store and the load, these barriers ensure the reader sees the fully initialised 'hyp_vcpu' object even if there were a lockless path or if the lock's own ordering guarantees were insufficient for nested object initialization.

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

References (3)

Vendor Advisories for CVE-2026-46147(2)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
linuxKernel @ 6.18.30—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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (136 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 8× in last 7d / 32× 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 214 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-46147?
CVE-2026-46147 is a medium vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix pin leak and publication ordering in pkvminitvcpu() Two bugs exist in the vCPU initialisation path: 1. If a check fails after hyppinshared_mem() succeeds, the cleanup path jumps to 'unlock' without calling…
When was CVE-2026-46147 disclosed?
CVE-2026-46147 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-46147 actively exploited?
CVE-2026-46147 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.3% of all scored CVEs.
How do I remediate CVE-2026-46147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46147, 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-46147

Explore →

Is Your Infrastructure Affected by CVE-2026-46147?

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

Start Free Scan →Browse All CVEs