CVE-2024-39298

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-38123 (ENISA EUVD) · GHSA-9m6x-4fj9-2p5c (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/memory-failure: fix handling of dissolved but not taken off from buddy pages

When I did memory failure tests recently, below panic occurs:

page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00 flags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff) raw: 06fffe0000000000 dead000000000100 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000009 00000000ffffffff 0000000000000000 page dumped because: VM_BUG_ON_PAGE(!PageBuddy(page)) ------------[ cut here ]------------ kernel BUG at include/linux/page-flags.h:1009! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:__del_page_from_free_list+0x151/0x180 RSP: 0018:ffffa49c90437998 EFLAGS: 00000046 RAX: 0000000000000035 RBX: 0000000000000009 RCX: ffff8dd8dfd1c9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff8dd8dfd1c9c0 RBP: ffffd901233b8000 R08: ffffffffab5511f8 R09: 0000000000008c69 R10: 0000000000003c15 R11: ffffffffab5511f8 R12: ffff8dd8fffc0c80 R13: 0000000000000001 R14: ffff8dd8fffc0c80 R15: 0000000000000009 FS: 00007ff916304740(0000) GS:ffff8dd8dfd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055eae50124c8 CR3: 00000008479e0000 CR4: 00000000000006f0 Call Trace: __rmqueue_pcplist+0x23b/0x520 get_page_from_freelist+0x26b/0xe40 __alloc_pages_noprof+0x113/0x1120 __folio_alloc_noprof+0x11/0xb0 alloc_buddy_hugetlb_folio.isra.0+0x5a/0x130 __alloc_fresh_hugetlb_folio+0xe7/0x140 alloc_pool_huge_folio+0x68/0x100 set_max_huge_pages+0x13d/0x340 hugetlb_sysctl_handler_common+0xe8/0x110 proc_sys_call_handler+0x194/0x280 vfs_write+0x387/0x550 ksys_write+0x64/0xe0 do_syscall_64+0xc2/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff916114887 RSP: 002b:00007ffec8a2fd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000055eae500e350 RCX: 00007ff916114887 RDX: 0000000000000004 RSI: 000055eae500e390 RDI: 0000000000000003 RBP: 000055eae50104c0 R08: 0000000000000000 R09: 000055eae50104c0 R10: 0000000000000077 R11: 0000000000000246 R12: 0000000000000004 R13: 0000000000000004 R14: 00007ff916216b80 R15: 00007ff916216a00 Modules linked in: mce_inject hwpoison_inject ---[ end trace 0000000000000000 ]---

And before the panic, there had an warning about bad page state:

BUG: Bad page state in process page-types pfn:8cee00 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00 flags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff) page_type: 0xffffff7f(buddy) raw: 06fffe0000000000 ffffd901241c0008 ffffd901240f8008 0000000000000000 raw: 0000000000000000 0000000000000009 00000000ffffff7f 0000000000000000 page dumped because: nonzero mapcount Modules linked in: mce_inject hwpoison_inject CPU: 8 PID: 154211 Comm: page-types Not tainted 6.9.0-rc4-00499-g5544ec3178e2-dirty #22 Call Trace: dump_stack_lvl+0x83/0xa0 bad_page+0x63/0xf0 free_unref_page+0x36e/0x5c0 unpoison_memory+0x50b/0x630 simple_attr_write_xsigned.constprop.0.isra.0+0xb3/0x110 debugfs_attr_write+0x42/0x60 full_proxy_write+0x5b/0x80 vfs_write+0xcd/0x550 ksys_write+0x64/0xe0 do_syscall_64+0xc2/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f189a514887 RSP: 002b:00007ffdcd899718 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f189a514887 RDX: 0000000000000009 RSI: 00007ffdcd899730 RDI: 0000000000000003 RBP: 00007ffdcd8997a0 R08: 0000000000000000 R09: 00007ffdcd8994b2 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffdcda199a8 R13: 0000000000404af1 R14: 000000000040ad78 R15: 00007f189a7a5040

The root cause should be the below race:

memory_failure try_memory_failure_hugetlb me_huge_page __page_handle_poison dissolve_free_hugetlb_folio drain_all_pages -- Buddy page can be isolated e.g. for compaction. take_page_off_buddy -- Failed as page is not in the ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2024

Last Modified

November 3, 2025

References (5)

Vendor Advisories for CVE-2024-39298(1)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.1.95 (fixes >=6.0.0)—osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.98-1 (25 versions)
  • every version up to 6.1.99-1: fixed in 6.1.99-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 215 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-39298?
CVE-2024-39298 is a medium-severity vulnerability; its CVE record was published on June 25, 2024. In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix handling of dissolved but not taken off from buddy pages When I did memory failure tests recently, below panic occurs: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00 flags:…
When was the CVE record for CVE-2024-39298 published?
The CVE record for CVE-2024-39298 was published on June 25, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-39298 actively exploited?
CVE-2024-39298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39298?
CVE-2024-39298 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-39298?
A fix for CVE-2024-39298 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-39298 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-39298

Explore →

Is Your Infrastructure Affected by CVE-2024-39298?

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

Book a Demo →Browse All CVEs