CVE-2024-36028

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-35838 (ENISA EUVD)Source: ENISA EUVD

4.7EG
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: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio()

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

DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 8 PID: 1011 at kernel/locking/lockdep.c:232 __lock_acquire+0xccb/0x1ca0 Modules linked in: mce_inject hwpoison_inject CPU: 8 PID: 1011 Comm: bash Kdump: loaded Not tainted 6.9.0-rc3-next-20240410-00012-gdb69f219f4be #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 RIP: 0010:__lock_acquire+0xccb/0x1ca0 RSP: 0018:ffffa7a1c7fe3bd0 EFLAGS: 00000082 RAX: 0000000000000000 RBX: eb851eb853975fcf RCX: ffffa1ce5fc1c9c8 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffffa1ce5fc1c9c0 RBP: ffffa1c6865d3280 R08: ffffffffb0f570a8 R09: 0000000000009ffb R10: 0000000000000286 R11: ffffffffb0f2ad50 R12: ffffa1c6865d3d10 R13: ffffa1c6865d3c70 R14: 0000000000000000 R15: 0000000000000004 FS: 00007ff9f32aa740(0000) GS:ffffa1ce5fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff9f3134ba0 CR3: 00000008484e4000 CR4: 00000000000006f0 Call Trace: lock_acquire+0xbe/0x2d0 _raw_spin_lock_irqsave+0x3a/0x60 hugepage_subpool_put_pages.part.0+0xe/0xc0 free_huge_folio+0x253/0x3f0 dissolve_free_huge_page+0x147/0x210 __page_handle_poison+0x9/0x70 memory_failure+0x4e6/0x8c0 hard_offline_page_store+0x55/0xa0 kernfs_fop_write_iter+0x12c/0x1d0 vfs_write+0x380/0x540 ksys_write+0x64/0xe0 do_syscall_64+0xbc/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff9f3114887 RSP: 002b:00007ffecbacb458 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007ff9f3114887 RDX: 000000000000000c RSI: 0000564494164e10 RDI: 0000000000000001 RBP: 0000564494164e10 R08: 00007ff9f31d1460 R09: 000000007fffffff R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000000c R13: 00007ff9f321b780 R14: 00007ff9f3217600 R15: 00007ff9f3216a00 Kernel panic - not syncing: kernel: panic_on_warn set ... CPU: 8 PID: 1011 Comm: bash Kdump: loaded Not tainted 6.9.0-rc3-next-20240410-00012-gdb69f219f4be #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Call Trace: panic+0x326/0x350 check_panic_on_warn+0x4f/0x50 __warn+0x98/0x190 report_bug+0x18e/0x1a0 handle_bug+0x3d/0x70 exc_invalid_op+0x18/0x70 asm_exc_invalid_op+0x1a/0x20 RIP: 0010:__lock_acquire+0xccb/0x1ca0 RSP: 0018:ffffa7a1c7fe3bd0 EFLAGS: 00000082 RAX: 0000000000000000 RBX: eb851eb853975fcf RCX: ffffa1ce5fc1c9c8 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffffa1ce5fc1c9c0 RBP: ffffa1c6865d3280 R08: ffffffffb0f570a8 R09: 0000000000009ffb R10: 0000000000000286 R11: ffffffffb0f2ad50 R12: ffffa1c6865d3d10 R13: ffffa1c6865d3c70 R14: 0000000000000000 R15: 0000000000000004 lock_acquire+0xbe/0x2d0 _raw_spin_lock_irqsave+0x3a/0x60 hugepage_subpool_put_pages.part.0+0xe/0xc0 free_huge_folio+0x253/0x3f0 dissolve_free_huge_page+0x147/0x210 __page_handle_poison+0x9/0x70 memory_failure+0x4e6/0x8c0 hard_offline_page_store+0x55/0xa0 kernfs_fop_write_iter+0x12c/0x1d0 vfs_write+0x380/0x540 ksys_write+0x64/0xe0 do_syscall_64+0xbc/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff9f3114887 RSP: 002b:00007ffecbacb458 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007ff9f3114887 RDX: 000000000000000c RSI: 0000564494164e10 RDI: 0000000000000001 RBP: 0000564494164e10 R08: 00007ff9f31d1460 R09: 000000007fffffff R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000000c R13: 00007ff9f321b780 R14: 00007ff9f3217600 R15: 00007ff9f3216a00

After git bisecting and digging into the code, I believe the root cause is that _deferred_list field of folio is unioned with _hugetlb_subpool field. In __update_and_free_hugetlb_folio(), folio->_deferred_ ---truncated---

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 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
7th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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

May 30, 2024

Last Modified

September 18, 2025

References (4)

Vendor Advisories for CVE-2024-36028(1)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.1.91 (fixes >=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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36028?
CVE-2024-36028 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() When I did memory failure tests recently, below warning occurs: DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 8 PID: 1011 at kernel/locking/lockdep.c:232…
When was the CVE record for CVE-2024-36028 published?
The CVE record for CVE-2024-36028 was published on May 30, 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 September 18, 2025; the record at its source may have been updated since.
Is CVE-2024-36028 actively exploited?
CVE-2024-36028 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36028?
CVE-2024-36028 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-36028?
A fix for CVE-2024-36028 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36028 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-36028

Explore →

Is Your Infrastructure Affected by CVE-2024-36028?

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

Book a Demo →Browse All CVEs