CVE-2026-64527: drm/hyperv: validate VMBus packet size in receive callback
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 049a6b474823049fe60212f25f26e4b30f44ee8f, 164dc7bf17609340233c6bf4f66bb7c7008a0511, 57d5d697642e05d5dd2d40660817765943dd709f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 049a6b474823049fe60212f25f26e4b30f44ee8f, 164dc7bf17609340233c6bf4f66bb7c7008a0511, 57d5d697642e05d5dd2d40660817765943dd709f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Jul 25, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before 57d5d697642e05d5dd2d40660817765943dd709faffected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before f5251226551bfec98c4705641b6f94ff1f238d91affected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before 049a6b474823049fe60212f25f26e4b30f44ee8faffected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before 588c84b461393ff1998ac7b97b04f953f642e0dfaffected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before 164dc7bf17609340233c6bf4f66bb7c7008a0511affected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before c8974d96b6a5496f33dc69a3ce28a7bf5078def4affected · git
- 76c56a5affeba1e163b66b9d8cc192e6154466f0 and later · before 7f87763f47a3c22fb50265a00619ef10f2394b18affected · git
- before 5.14not affected · semver
- 5.15.210 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64525Jul 25, 2026 · xfrm: move policy_bydst RCU sync from per-netns .exit to .pre_exit0Monitor
- ← EarlierCVE-2026-64526Jul 25, 2026 · ethtool: tsconfig: fix missing ethnl_ops_complete()0Monitor
- Later →CVE-2026-64528Jul 25, 2026 · tty: serial: samsung: Remove redundant port lock acquisition in rx helpers0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 049a6b474823049fe60212f25f26e4b30f44ee8f | Vendor (CNA) |
| Linux Linux | 164dc7bf17609340233c6bf4f66bb7c7008a0511 | Vendor (CNA) |
| Linux Linux | 57d5d697642e05d5dd2d40660817765943dd709f | Vendor (CNA) |
| Linux Linux | 588c84b461393ff1998ac7b97b04f953f642e0df | Vendor (CNA) |
| Linux Linux | 7f87763f47a3c22fb50265a00619ef10f2394b18 | Vendor (CNA) |
| Linux Linux | c8974d96b6a5496f33dc69a3ce28a7bf5078def4 | Vendor (CNA) |
| Linux Linux | f5251226551bfec98c4705641b6f94ff1f238d91 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0636 · Jul 27, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/164dc7bf17609340233c6bf4f66bb7c7008a0511
- git.kernel.org/stable/c/57d5d697642e05d5dd2d40660817765943dd709f
- git.kernel.org/stable/c/588c84b461393ff1998ac7b97b04f953f642e0df
- git.kernel.org/stable/c/7f87763f47a3c22fb50265a00619ef10f2394b18
- git.kernel.org/stable/c/c8974d96b6a5496f33dc69a3ce28a7bf5078def4
- git.kernel.org/stable/c/f5251226551bfec98c4705641b6f94ff1f238d91
Vendor advisories and official records. Exploit/PoC links are deliberately left out.