CVE-2026-52969KVM: Reject wrapped offset in kvm_reset_dirty_gfn()
- 7.0HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% 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: KVM: Reject wrapped offset in kvm_reset_dirty_gfn() kvm_reset_dirty_gfn() guards the gfn range with if (!memslot || (offset + __fls(mask)) >= memslot->npages) return; but offset is u64 and the addition is unchecked. The check can be silently bypassed by a u64 wrap. The dirty ring backing those entries is MAP_SHARED at KVM_DIRTY_LOG_PAGE_OFFSET of the vcpu fd, so the VMM can rewrite the slot and offset fields of any entry between when the kernel pushes them and when KVM_RESET_DIRTY_RINGS consumes them. On reset, kvm_dirty_ring_reset() re-reads the values via READ_ONCE() and feeds them straight back into this check; only the flags handshake is treated as the handover, the slot/offset payload is taken on trust. Crafting two entries entry[i].offset = 0xffffffffffffffc1 entry[i+1].offset = 0 makes the coalescing loop in kvm_dirty_ring_reset() compute delta = (s64)(0 - 0xffffffffffffffc1) = 63 which falls in [0, BITS_PER_LONG), so it folds entry[i+1] into the existing mask by setting bit 63. The trailing kvm_reset_dirty_gfn() call then sees offset = 0xffffffffffffffc1 and __fls(mask) = 63; the sum is 0 in u64 and the bounds check passes. That offset propagates into kvm_arch_mmu_enable_log_dirty_pt_masked() unchanged. On the legacy MMU path -- kvm_memslots_have_rmaps() == true, i.e. shadow paging, any VM that has allocated shadow roots, or a write-tracked slot -- it reaches gfn_to_rmap(), which indexes slot->arch.rmap[0][] with a near-U64_MAX gfn. That is an out-of-bounds load of a kvm_rmap_head, followed by a conditional clear of PT_WRITABLE_MASK in whatever the loaded pointer points at. The path is reachable from any process holding /dev/kvm. Range-check offset on its own first, so the addition cannot wrap. memslot->npages is bounded well below U64_MAX, so once offset < npages holds, offset + __fls(mask) (with __fls(mask) < BITS_PER_LONG) stays in range.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 21 days later
· 21 days later
Record updated
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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhat-SADPADP (enrichment) | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < 74f1a22f7a80f03d28ad8551a2d25d563433addf
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < 0eb281eb95b2d4eea4db1da5fe91023aecc97095
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < 01b71b930f15728aa8599478a7ce90c19dcd9fc2
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < b315b033a877b1ee6d827810b5d7bb4392ffcf8d
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < 0d419c23bb11b5c9664de777c47c1f04a235882d
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < ecf9b3ea7847fe14f34b8c41f00de1eb95c747da
- affected fb04a1eddb1a65b6588a021bdc132270d5ae48bb – < 577a8d3bae0531f0e5ccfac919cd8192f920a804
- affected 5.11
- unaffected < 5.11
- unaffected 5.15.209 – ≤ 5.15.*
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.141 – ≤ 6.6.*
- unaffected 6.12.91 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References10
- https://git.kernel.org/stable/c/74f1a22f7a80f03d28ad8551a2d25d563433addf (opens in a new tab)
- https://git.kernel.org/stable/c/0eb281eb95b2d4eea4db1da5fe91023aecc97095 (opens in a new tab)
- https://git.kernel.org/stable/c/01b71b930f15728aa8599478a7ce90c19dcd9fc2 (opens in a new tab)
- https://git.kernel.org/stable/c/b315b033a877b1ee6d827810b5d7bb4392ffcf8d (opens in a new tab)
- https://git.kernel.org/stable/c/0d419c23bb11b5c9664de777c47c1f04a235882d (opens in a new tab)
- https://git.kernel.org/stable/c/ecf9b3ea7847fe14f34b8c41f00de1eb95c747da (opens in a new tab)
- https://git.kernel.org/stable/c/577a8d3bae0531f0e5ccfac919cd8192f920a804 (opens in a new tab)
- https://access.redhat.com/security/cve/CVE-2026-52969 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2492434 (opens in a new tab)issue-trackingx_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52969.json (opens in a new tab)x_sadp-csaf-vex
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-38837 (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-52969)Record last updated .