CVE-2026-64527drm/hyperv: validate VMBus packet size in receive callback
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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().
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Awaiting Analysis.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < 57d5d697642e05d5dd2d40660817765943dd709f
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < f5251226551bfec98c4705641b6f94ff1f238d91
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < 049a6b474823049fe60212f25f26e4b30f44ee8f
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < 588c84b461393ff1998ac7b97b04f953f642e0df
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < 164dc7bf17609340233c6bf4f66bb7c7008a0511
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < c8974d96b6a5496f33dc69a3ce28a7bf5078def4
- affected 76c56a5affeba1e163b66b9d8cc192e6154466f0 – < 7f87763f47a3c22fb50265a00619ef10f2394b18
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.176 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.93 – ≤ 6.12.*
- unaffected 6.18.35 – ≤ 6.18.*
- unaffected 7.0.12 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/57d5d697642e05d5dd2d40660817765943dd709f (opens in a new tab)
- https://git.kernel.org/stable/c/f5251226551bfec98c4705641b6f94ff1f238d91 (opens in a new tab)
- https://git.kernel.org/stable/c/049a6b474823049fe60212f25f26e4b30f44ee8f (opens in a new tab)
- https://git.kernel.org/stable/c/588c84b461393ff1998ac7b97b04f953f642e0df (opens in a new tab)
- https://git.kernel.org/stable/c/164dc7bf17609340233c6bf4f66bb7c7008a0511 (opens in a new tab)
- https://git.kernel.org/stable/c/c8974d96b6a5496f33dc69a3ce28a7bf5078def4 (opens in a new tab)
- https://git.kernel.org/stable/c/7f87763f47a3c22fb50265a00619ef10f2394b18 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-49039 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64527)Record last updated .