CVE-2026-64527

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week

Also known asEUVD-2026-49039 (ENISA EUVD) · GHSA-86px-9vhr-gg2j (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/hyperv: validate VMBus packet size in receive callback

hyperv_receive_sub() reads msg->vid_hdr.type and dispatches into one of four message-type branches without knowing how many bytes the host wrote into hv->recv_buf. The completion path then runs memcpy(hv->init_buf, msg, VMBUS_MAX_PACKET_SIZE), so the consumer that wakes on wait_for_completion_timeout() can read up to 16 KiB of residue from a prior message as if it were the response payload.

Pass bytes_recvd into hyperv_receive_sub() and reject any packet that does not cover the pipe + synthvid header. A single switch on msg->vid_hdr.type then computes the type-specific payload size: the three completion-driving types (SYNTHVID_VERSION_RESPONSE, SYNTHVID_RESOLUTION_RESPONSE, SYNTHVID_VRAM_LOCATION_ACK) fall through to a shared exit that requires that size before memcpy/complete, while SYNTHVID_FEATURE_CHANGE validates its own payload and returns before reading is_dirt_needed. Unknown types are dropped.

SYNTHVID_RESOLUTION_RESPONSE is variable length: the host fills resolution_count entries, not the full SYNTHVID_MAX_RESOLUTION_COUNT array. Validate the fixed prefix first so resolution_count can be read, bound it against the array, then require only the count-sized array, so the shorter responses the host actually sends are accepted.

Only run the sub-handler when vmbus_recvpacket() returned success. The memcpy length is bytes_recvd, which is bounded by VMBUS_MAX_PACKET_SIZE only on a successful receive; on -ENOBUFS vmbus_recvpacket() instead reports the required length, which can exceed hv->recv_buf, so copying bytes_recvd would read and write past the 16 KiB buffers. Gating on the success return keeps the copy bounded. The nonzero-return path is itself a malformed-message case and is now logged rather than silently skipped; channel recovery is not attempted.

Rejected packets are reported via drm_err_ratelimited() rather than silently dropped, matching the CoCo-hardened pattern in hv_kvp_onchannelcallback().

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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: the BOD 26-04 block below.

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.

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

July 25, 2026

Last Modified

July 25, 2026

Vendor Advisories for CVE-2026-64527(1)

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

Patch Availability(18)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

All Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 12× in last 7d / 41× 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 100 of 139 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. None are among the latest 100 rows. The 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2026-64527?
CVE-2026-64527 is a vulnerability whose severity is not yet rated; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/hyperv: validate VMBus packet size in receive callback hypervreceivesub() reads msg->vid_hdr.type and dispatches into one of four message-type branches without knowing how many bytes the host wrote into hv->recv_buf. The…
When was the CVE record for CVE-2026-64527 published?
The CVE record for CVE-2026-64527 was published on July 25, 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 July 25, 2026; the record at its source may have been updated since.
Is CVE-2026-64527 actively exploited?
CVE-2026-64527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-64527?
A fix for CVE-2026-64527 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64527 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-64527

Explore →

Is Your Infrastructure Affected by CVE-2026-64527?

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