CVE-2024-35804

Description

A flaw was found in the KVM (Kernel-based Virtual Machine) subsystem of the Linux kernel on x86 architectures. When emulating atomic operations on behalf of a guest, the hypervisor fails to mark modified memory pages as dirty. When a virtual machine undergoes live migration, this omission causes the host to miss memory updates, resulting in guest memory corruption and system instability.

Statement

This vulnerability is rated with a Low severity because it only triggers under very specific timing conditions during live migration and cannot be exploited to compromise or escape the host hypervisor. On x86 virtualization hosts, emulated atomic memory instructions are omitted from dirty page tracking logs during guest migration. Consequently, while an active guest might encounter memory inconsistencies after being migrated, host integrity and confidentiality remain intact.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.55.58.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedChanged
ConfidentialityNoneNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity,Confidentiality,Other

Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic

If access to a shared resource is not synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.