CVE-2024-35877

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-05-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

x86/mm/pat: fix VM_PAT handling in COW mappings

PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings.

Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range().

In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory.

To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that.

We will now properly handle untrack_pfn() with COW mappings, where we don't need the cachemode. We'll have to fail fork()->track_pfn_copy() if the first page was replaced by an anon folio, though: we'd have to store the cachemode in the VMA to make this work, likely growing the VMA size.

For now, lets keep it simple and let track_pfn_copy() just fail in that case: it would have failed in the past with swap/nonswap entries already, and it would have done the wrong thing with anon folios.

Simple reproducer to trigger the WARN_ON_ONCE() in untrack_pfn():

<--- C reproducer ---> #include #include #include #include

int main(void) { struct io_uring_params p = {}; int ring_fd; size_t size; char *map;

ring_fd = io_uring_setup(1, &p); if (ring_fd < 0) { perror("io_uring_setup"); return 1; } size = p.sq_off.array + p.sq_entries * sizeof(unsigned);

/* Map the submission queue ring MAP_PRIVATE */ map = mmap(0, size, PROT_READ | PROT_WRITE, MAP_PRIVATE, ring_fd, IORING_OFF_SQ_RING); if (map == MAP_FAILED) { perror("mmap"); return 1; }

/* We have at least one page. Let's COW it. */ *map = 0; pause(); return 0; } <--- C reproducer --->

On a system with 16 GiB RAM and swap configured: # ./iouring & # memhog 16G # killall iouring [ 301.552930] ------------[ cut here ]------------ [ 301.553285] WARNING: CPU: 7 PID: 1402 at arch/x86/mm/pat/memtype.c:1060 untrack_pfn+0xf4/0x100 [ 301.553989] Modules linked in: binfmt_misc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_g [ 301.558232] CPU: 7 PID: 1402 Comm: iouring Not tainted 6.7.5-100.fc38.x86_64 #1 [ 301.558772] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebu4 [ 301.559569] RIP: 0010:untrack_pfn+0xf4/0x100 [ 301.559893] Code: 75 c4 eb cf 48 8b 43 10 8b a8 e8 00 00 00 3b 6b 28 74 b8 48 8b 7b 30 e8 ea 1a f7 000 [ 301.561189] RSP: 0018:ffffba2c0377fab8 EFLAGS: 00010282 [ 301.561590] RAX: 00000000ffffffea RBX: ffff9208c8ce9cc0 RCX: 000000010455e047 [ 301.562105] RDX: 07fffffff0eb1e0a RSI: 0000000000000000 RDI: ffff9208c391d200 [ 301.562628] RBP: 0000000000000000 R08: ffffba2c0377fab8 R09: 0000000000000000 [ 301.563145] R10: ffff9208d2292d50 R11: 0000000000000002 R12: 00007fea890e0000 [ 301.563669] R13: 0000000000000000 R14: ffffba2c0377fc08 R15: 0000000000000000 [ 301.564186] FS: 0000000000000000(0000) GS:ffff920c2fbc0000(0000) knlGS:0000000000000000 [ 301.564773] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 301.565197] CR2: 00007fea88ee8a20 CR3: 00000001033a8000 CR4: 0000000000750ef0 [ 301.565725] PKRU: 55555554 [ 301.565944] Call Trace: [ 301.566148] [ 301.566325] ? untrack_pfn+0xf4/0x100 [ 301.566618] ? __warn+0x81/0x130 [ 301.566876] ? untrack_pfn+0xf4/0x100 [ 3 ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
16.7%
KEV
Not listed

Published

May 19, 2024

Last Modified

May 12, 2026

References (19)

Vendor Advisories for CVE-2024-35877(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-05-22ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-05-22ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-05-22ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-05-22ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-05-22ubuntu
ubuntulinux-tools-iot (5.4.0.1040.38) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-05-22ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-05-22ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-05-22ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.231.215) @ bionic2026-05-22ubuntu
ubuntulinux-tools-azure (4.15.0.1183.198~14.04.1) @ trusty2026-05-22ubuntu
ubuntulinux-tools-oracle (4.15.0.1137.148~16.04.1) @ xenial2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-05-22ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.261.267) @ xenial2026-05-22ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-05-22ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-05-22ubuntu
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-05-22ubuntu
redhatkernel-0:5.14.0-427.68.1.el9_42025-05-14redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-rt-0:4.18.0-553.22.1.rt7.363.el8_102024-09-24redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat
linuxKernel @ 4.19.312osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 12× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-07-23 02:37 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-19 02:28 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:59 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-13 22:29 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-12 05:45 UTCEPSS rescore
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-11 08:26 UTCEPSS rescore
  22. 2026-07-11 05:41 UTCOSV refresh
  23. 2026-07-09 19:09 UTCEPSS rescore
  24. 2026-07-08 15:14 UTCEPSS rescore
  25. 2026-07-08 15:13 UTCEPSS rescore
Show 75 more
  1. 2026-07-07 13:45 UTCEPSS rescore
  2. 2026-07-06 16:26 UTCEPSS rescore
  3. 2026-07-06 02:22 UTCEPSS rescore
  4. 2026-07-06 02:22 UTCEPSS rescore
  5. 2026-07-05 02:29 UTCEPSS rescore
  6. 2026-07-04 06:30 UTCEPSS rescore
  7. 2026-07-01 15:05 UTCEPSS rescore
  8. 2026-06-30 23:21 UTCEPSS rescore
  9. 2026-06-30 23:21 UTCEPSS rescore
  10. 2026-06-29 14:05 UTCEPSS rescore
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 14:06 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-27 03:07 UTCEPSS rescore
  16. 2026-06-27 03:07 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 12:26 UTCOSV refresh
  25. 2026-06-21 14:55 UTCEPSS rescore
  26. 2026-06-21 14:55 UTCEPSS rescore
  27. 2026-06-21 01:58 UTCEPSS rescore
  28. 2026-06-21 01:58 UTCEPSS rescore
  29. 2026-06-19 19:25 UTCEPSS rescore
  30. 2026-06-19 19:25 UTCEPSS rescore
  31. 2026-06-18 17:52 UTCEPSS rescore
  32. 2026-06-18 17:51 UTCEPSS rescore
  33. 2026-06-17 17:52 UTCEPSS rescore
  34. 2026-06-16 17:52 UTCEPSS rescore
  35. 2026-06-16 17:52 UTCEPSS rescore
  36. 2026-06-15 17:47 UTCEPSS rescore
  37. 2026-06-14 23:16 UTCEPSS rescore
  38. 2026-06-12 23:11 UTCEPSS rescore
  39. 2026-06-11 13:59 UTCEPSS rescore
  40. 2026-06-10 22:17 UTCEPSS rescore
  41. 2026-06-10 13:21 UTCEPSS rescore
  42. 2026-06-08 14:16 UTCEPSS rescore
  43. 2026-06-07 15:24 UTCEPSS rescore
  44. 2026-06-07 15:24 UTCEPSS rescore
  45. 2026-06-06 13:46 UTCEPSS rescore
  46. 2026-06-06 13:46 UTCEPSS rescore
  47. 2026-06-05 22:46 UTCEPSS rescore
  48. 2026-06-05 22:46 UTCEPSS rescore
  49. 2026-06-05 06:09 UTCEPSS rescore
  50. 2026-06-05 06:09 UTCEPSS rescore
  51. 2026-06-04 19:09 UTCOSV refresh
  52. 2026-06-04 13:11 UTCEPSS rescore
  53. 2026-06-04 13:11 UTCEPSS rescore
  54. 2026-06-02 20:12 UTCEPSS rescore
  55. 2026-06-01 13:51 UTCEPSS rescore
  56. 2026-06-01 13:51 UTCEPSS rescore
  57. 2026-05-31 00:15 UTCEPSS rescore
  58. 2026-05-31 00:15 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-28 13:44 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-27 13:40 UTCEPSS rescore
  65. 2026-05-26 13:43 UTCEPSS rescore
  66. 2026-05-26 13:43 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-26 07:18 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-22 21:16 UTCEPSS rescore
  71. 2026-05-22 21:16 UTCEPSS rescore
  72. 2026-05-22 21:16 UTCEPSS rescore
  73. 2026-05-22 21:16 UTCEPSS rescore
  74. 2026-05-22 01:43 UTCEG score recompute
  75. 2026-05-22 01:43 UTCVendor advisory

Frequently asked(5)

What is CVE-2024-35877?
CVE-2024-35877 is a medium vulnerability published on May 19, 2024. In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the…
When was CVE-2024-35877 disclosed?
CVE-2024-35877 was first published in the National Vulnerability Database on May 19, 2024, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-35877 actively exploited?
CVE-2024-35877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-35877?
CVE-2024-35877 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-35877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-35877, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-35877

Explore →

Is Your Infrastructure Affected by CVE-2024-35877?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.