{"api_version":"1","generated_at":"2026-08-28T17:26:44+00:00","cve":"CVE-2026-80702","urls":{"html":"https://cve.report/CVE-2026-80702","api":"https://cve.report/api/cve/CVE-2026-80702.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80702","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80702"},"summary":{"title":"drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size\n\nTwo sites in vmwgfx_resource.c assign boolean literals to\nres->guest_memory_size, which is an unsigned long allocation-size\nfield; the intended target is the adjacent res->guest_memory_dirty\nbitfield.  After the assignments the field holds 0 or 1 instead of\nthe resource's MOB allocation size:\n\n  - vmw_resource_release()       writes 0 (false), and\n  - vmw_resource_unbind_list()   writes 1 (true).\n\nSubsequent revalidation paths read guest_memory_size when computing\nthe dirty page range (vmw_bo_dirty_transfer_to_res()) and the buffer\nallocation size (vmw_resource_buf_alloc()), producing zero-length\nwalks or wrap-around ranges that read or write past the MOB bitmap.\nThe dirty-tracking intent of the original code (mark the resource as\ndirtied since the last sync) is also lost, since guest_memory_dirty\nis never updated.\n\nRename both assignments to guest_memory_dirty.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:55","updated_at":"2026-08-28 08:16:55"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6","name":"https://git.kernel.org/stable/c/9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa","name":"https://git.kernel.org/stable/c/83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/282f261cb035e5f01a486f76d356b7e9dbfba73f","name":"https://git.kernel.org/stable/c/282f261cb035e5f01a486f76d356b7e9dbfba73f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/21bbe38faee4a195d33a93e3908e307807f7745d","name":"https://git.kernel.org/stable/c/21bbe38faee4a195d33a93e3908e307807f7745d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3b2bb16a5b622867140d69925db411ac8ecb3b2b","name":"https://git.kernel.org/stable/c/3b2bb16a5b622867140d69925db411ac8ecb3b2b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80702","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80702","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 668b206601c5f5063e03b76784a0d3024fa2b249 21bbe38faee4a195d33a93e3908e307807f7745d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 668b206601c5f5063e03b76784a0d3024fa2b249 9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 668b206601c5f5063e03b76784a0d3024fa2b249 282f261cb035e5f01a486f76d356b7e9dbfba73f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 668b206601c5f5063e03b76784a0d3024fa2b249 3b2bb16a5b622867140d69925db411ac8ecb3b2b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 668b206601c5f5063e03b76784a0d3024fa2b249 83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.4","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.4 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.151 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.103 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/vmwgfx/vmwgfx_resource.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"21bbe38faee4a195d33a93e3908e307807f7745d","status":"affected","version":"668b206601c5f5063e03b76784a0d3024fa2b249","versionType":"git"},{"lessThan":"9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6","status":"affected","version":"668b206601c5f5063e03b76784a0d3024fa2b249","versionType":"git"},{"lessThan":"282f261cb035e5f01a486f76d356b7e9dbfba73f","status":"affected","version":"668b206601c5f5063e03b76784a0d3024fa2b249","versionType":"git"},{"lessThan":"3b2bb16a5b622867140d69925db411ac8ecb3b2b","status":"affected","version":"668b206601c5f5063e03b76784a0d3024fa2b249","versionType":"git"},{"lessThan":"83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa","status":"affected","version":"668b206601c5f5063e03b76784a0d3024fa2b249","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/vmwgfx/vmwgfx_resource.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.4"},{"lessThan":"6.4","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.151","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.103","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.151","versionStartIncluding":"6.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.103","versionStartIncluding":"6.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"6.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"6.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.4","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size\n\nTwo sites in vmwgfx_resource.c assign boolean literals to\nres->guest_memory_size, which is an unsigned long allocation-size\nfield; the intended target is the adjacent res->guest_memory_dirty\nbitfield.  After the assignments the field holds 0 or 1 instead of\nthe resource's MOB allocation size:\n\n  - vmw_resource_release()       writes 0 (false), and\n  - vmw_resource_unbind_list()   writes 1 (true).\n\nSubsequent revalidation paths read guest_memory_size when computing\nthe dirty page range (vmw_bo_dirty_transfer_to_res()) and the buffer\nallocation size (vmw_resource_buf_alloc()), producing zero-length\nwalks or wrap-around ranges that read or write past the MOB bitmap.\nThe dirty-tracking intent of the original code (mark the resource as\ndirtied since the last sync) is also lost, since guest_memory_dirty\nis never updated.\n\nRename both assignments to guest_memory_dirty."}],"providerMetadata":{"dateUpdated":"2026-08-28T06:53:05.253Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/21bbe38faee4a195d33a93e3908e307807f7745d"},{"url":"https://git.kernel.org/stable/c/9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6"},{"url":"https://git.kernel.org/stable/c/282f261cb035e5f01a486f76d356b7e9dbfba73f"},{"url":"https://git.kernel.org/stable/c/3b2bb16a5b622867140d69925db411ac8ecb3b2b"},{"url":"https://git.kernel.org/stable/c/83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa"}],"title":"drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80702","datePublished":"2026-08-28T06:53:05.253Z","dateReserved":"2026-08-26T14:34:25.786Z","dateUpdated":"2026-08-28T06:53:05.253Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:55","lastModifiedDate":"2026-08-28 08:16:55","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80702","Ordinal":"1","Title":"drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size","CVE":"CVE-2026-80702","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80702","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size\n\nTwo sites in vmwgfx_resource.c assign boolean literals to\nres->guest_memory_size, which is an unsigned long allocation-size\nfield; the intended target is the adjacent res->guest_memory_dirty\nbitfield.  After the assignments the field holds 0 or 1 instead of\nthe resource's MOB allocation size:\n\n  - vmw_resource_release()       writes 0 (false), and\n  - vmw_resource_unbind_list()   writes 1 (true).\n\nSubsequent revalidation paths read guest_memory_size when computing\nthe dirty page range (vmw_bo_dirty_transfer_to_res()) and the buffer\nallocation size (vmw_resource_buf_alloc()), producing zero-length\nwalks or wrap-around ranges that read or write past the MOB bitmap.\nThe dirty-tracking intent of the original code (mark the resource as\ndirtied since the last sync) is also lost, since guest_memory_dirty\nis never updated.\n\nRename both assignments to guest_memory_dirty.","Type":"Description","Title":"drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size"}]}}}