SECUFOCUSNOW
Home›CVE index›CVE-2026-52969
Review reviewHigh

CVE-2026-52969

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

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_ri...

CVSS
7.8
EPSS
0.15%
4.87% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.8

Vulnerability overview

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_ri...

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6
Affected versions
>= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < 74f1a22f7a80f03d28ad8551a2d25d563433addf, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < 0eb281eb95b2d4eea4db1da5fe91023aecc97095, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < 01b71b930f15728aa8599478a7ce90c19dcd9fc2, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < b315b033a877b1ee6d827810b5d7bb4392ffcf8d, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < 0d419c23bb11b5c9664de777c47c1f04a235882d, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < ecf9b3ea7847fe14f34b8c41f00de1eb95c747da, >= fb04a1eddb1a65b6588a021bdc132270d5ae48bb < 577a8d3bae0531f0e5ccfac919cd8192f920a804, >= 5.11, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10, 7.1
Fixed versions
5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-129, CWE-190