Skip to content
Noroxi
CVE-2024-35804· NVD / CVE Program· CNA Linux

KVM: x86: Mark target gfn of emulated atomic instruction as dirty

Noroxi assessment

Priority: Monitor (action score 22/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.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 225d587a073584946c05c9b7651d637bd45c0c71, 5.15.154, 5.18.
  • Severity is disputed: the assigning authority (CNA) scores it 8.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 225d587a073584946c05c9b7651d637bd45c0c71, 5.15.154, 5.18 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: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM did before the buggy commit. Huge kudos to the folks on the Cc list (and many others), who did all the actual work of triaging and debugging. base-commit: 6769ea8da8a93ed4630f1ce64df6aafcaabfce64

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
8.8
3.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2024-35804

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

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

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15.58 and later · before 5.15.154
  • linux linux kernel5.17.13 and later · before 5.18
  • linux linux kernel5.18.2 and later · before 6.1.84
  • linux linux kernel6.2 and later · before 6.6.24
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.8

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

    • b0f294103f4cf733e23d3f0c4e5fd58e42998921, e964665cc7ca13a16992b205fce63554b9efc78b, 5.19affected
    • d97c0667c1e61ded6639117b4b9584a9c12b7e66 and later · before a9bd6bb6f02bf7132c1ab192ba62bbfa52df7d66affected · git
    • 1c2361f667f3648855ceae25f1332c18413fdb9f and later · before 726374dde5d608b15b9756bd52b6fc283fda7a06affected · git
    • 1c2361f667f3648855ceae25f1332c18413fdb9f and later · before 9d1b22e573a3789ed1f32033ee709106993ba551affected · git
    • 1c2361f667f3648855ceae25f1332c18413fdb9f and later · before 225d587a073584946c05c9b7651d637bd45c0c71affected · git
    • 1c2361f667f3648855ceae25f1332c18413fdb9f and later · before 910c57dfa4d113aae6571c2a8b9ae8c430975902affected · git
    • 5.15.58 and later · before 5.15.154affected · semver
    • 5.17.13 and later · before 5.18affected · semver
    • 5.18.2 and later · before 5.19affected · semver
    • before 5.19not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-1

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35801May 17, 2024 · x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD
    22Monitor
  • ← EarlierCVE-2024-35803May 17, 2024 · x86/efistub: Call mixed mode boot services on the firmware's stack
    22Monitor
  • Later →CVE-2024-35806May 17, 2024 · soc: fsl: qbman: Always disable interrupts when taking cgr_lock
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux225d587a073584946c05c9b7651d637bd45c0c71Vendor (CNA)
Linux Linux5.15.154Vendor (CNA)
Linux Linux5.18Vendor (CNA)
Linux Linux5.19Vendor (CNA)
Linux Linux726374dde5d608b15b9756bd52b6fc283fda7a06Vendor (CNA)
Linux Linux910c57dfa4d113aae6571c2a8b9ae8c430975902Vendor (CNA)
Linux Linux9d1b22e573a3789ed1f32033ee709106993ba551Vendor (CNA)
Linux Linuxa9bd6bb6f02bf7132c1ab192ba62bbfa52df7d66Vendor (CNA)
debian:linux6.1.85-1 · Debian:12Package 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.

EPSS, last 120 days

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.

Finders, 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).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-primary

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records