CVE-2024-57884

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 2025-01-15. 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-53787 (ENISA EUVD) · GHSA-qvj7-29h2-6r54 (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: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim()

The task sometimes continues looping in throttle_direct_reclaim() because allow_direct_reclaim(pgdat) keeps returning false.

#0 [ffff80002cb6f8d0] __switch_to at ffff8000080095ac #1 [ffff80002cb6f900] __schedule at ffff800008abbd1c #2 [ffff80002cb6f990] schedule at ffff800008abc50c #3 [ffff80002cb6f9b0] throttle_direct_reclaim at ffff800008273550 #4 [ffff80002cb6fa20] try_to_free_pages at ffff800008277b68 #5 [ffff80002cb6fae0] __alloc_pages_nodemask at ffff8000082c4660 #6 [ffff80002cb6fc50] alloc_pages_vma at ffff8000082e4a98 #7 [ffff80002cb6fca0] do_anonymous_page at ffff80000829f5a8 #8 [ffff80002cb6fce0] __handle_mm_fault at ffff8000082a5974 #9 [ffff80002cb6fd90] handle_mm_fault at ffff8000082a5bd4

At this point, the pgdat contains the following two zones:

NODE: 4 ZONE: 0 ADDR: ffff00817fffe540 NAME: "DMA32" SIZE: 20480 MIN/LOW/HIGH: 11/28/45 VM_STAT: NR_FREE_PAGES: 359 NR_ZONE_INACTIVE_ANON: 18813 NR_ZONE_ACTIVE_ANON: 0 NR_ZONE_INACTIVE_FILE: 50 NR_ZONE_ACTIVE_FILE: 0 NR_ZONE_UNEVICTABLE: 0 NR_ZONE_WRITE_PENDING: 0 NR_MLOCK: 0 NR_BOUNCE: 0 NR_ZSPAGES: 0 NR_FREE_CMA_PAGES: 0

NODE: 4 ZONE: 1 ADDR: ffff00817fffec00 NAME: "Normal" SIZE: 8454144 PRESENT: 98304 MIN/LOW/HIGH: 68/166/264 VM_STAT: NR_FREE_PAGES: 146 NR_ZONE_INACTIVE_ANON: 94668 NR_ZONE_ACTIVE_ANON: 3 NR_ZONE_INACTIVE_FILE: 735 NR_ZONE_ACTIVE_FILE: 78 NR_ZONE_UNEVICTABLE: 0 NR_ZONE_WRITE_PENDING: 0 NR_MLOCK: 0 NR_BOUNCE: 0 NR_ZSPAGES: 0 NR_FREE_CMA_PAGES: 0

In allow_direct_reclaim(), while processing ZONE_DMA32, the sum of inactive/active file-backed pages calculated in zone_reclaimable_pages() based on the result of zone_page_state_snapshot() is zero.

Additionally, since this system lacks swap, the calculation of inactive/ active anonymous pages is skipped.

crash> p nr_swap_pages nr_swap_pages = $1937 = { counter = 0 }

As a result, ZONE_DMA32 is deemed unreclaimable and skipped, moving on to the processing of the next zone, ZONE_NORMAL, despite ZONE_DMA32 having free pages significantly exceeding the high watermark.

The problem is that the pgdat->kswapd_failures hasn't been incremented.

crash> px ((struct pglist_data *) 0xffff00817fffe540)->kswapd_failures $1935 = 0x0

This is because the node deemed balanced. The node balancing logic in balance_pgdat() evaluates all zones collectively. If one or more zones (e.g., ZONE_DMA32) have enough free pages to meet their watermarks, the entire node is deemed balanced. This causes balance_pgdat() to exit early before incrementing the kswapd_failures, as it considers the overall memory state acceptable, even though some zones (like ZONE_NORMAL) remain under significant pressure.

The patch ensures that zone_reclaimable_pages() includes free pages (NR_FREE_PAGES) in its calculation when no other reclaimable pages are available (e.g., file-backed or anonymous pages). This change prevents zones like ZONE_DMA32, which have sufficient free pages, from being mistakenly deemed unreclaimable. By doing so, the patch ensures proper node balancing, avoids masking pressure on other zones like ZONE_NORMAL, and prevents infinite loops in throttle_direct_reclaim() caused by allow_direct_reclaim(pgdat) repeatedly returning false.

The kernel hangs due to a task stuck in throttle_direct_reclaim(), caused by a node being incorrectly deemed balanced despite pressure in certain zones, such as ZONE_NORMAL. This issue arises from zone_reclaimable_pages ---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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
12th
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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

January 15, 2025

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Oct 15, 2026
Patch available.
Web pageMentions a patch (unverified)

SSA-398330

https://cert-portal.siemens.com/productcert/html/ssa-398330.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4075-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6aaced5abd32e2a57cd94fd64f824514d0361da8
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58d0d02dbc67438fc80223fdd7bbc49cf0733284
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ff2302e8aeac7f2eedb551d7a89617283b5c6b2
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfb701192129803191c9cd6cdd1f82cd07f8de2c
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63eac98d6f0898229f515cb62fe4e4db2430e99c
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d675fefbaec3815b3ae0af1bebd97f27df3a05c8
Web page

mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66cd37660ec34ec444fe42f2277330ae4a36bb19

Vendor Advisories for CVE-2024-57884(2)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-10-15ubuntu
ubuntulinux-virtual (6.8.0-60.63) @ noble2026-10-15ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1028.31.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1012.14) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-10-15ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1026.27~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-10-15ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-10-15ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-gke (6.8.0-1025.29) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-10-15ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-15ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.4.289 (fixes >=4.8.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (33 versions)
  • every version up to 6.1.124-1: fixed in 6.1.124-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.9-1: fixed in 6.12.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.9-1: fixed in 6.12.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 8× in last 7d / 41× 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 95 of 200 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-57884?
CVE-2024-57884 is a medium-severity vulnerability; its CVE record was published on January 15, 2025. In the Linux kernel, the following vulnerability has been resolved: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() The task sometimes continues looping in throttle_direct_reclaim() because allow_direct_reclaim(pgdat) keeps returning false. #0…
When was the CVE record for CVE-2024-57884 published?
The CVE record for CVE-2024-57884 was published on January 15, 2025. 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-57884 actively exploited?
CVE-2024-57884 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-57884?
CVE-2024-57884 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-57884?
A fix for CVE-2024-57884 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-57884 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-57884

Explore →

Is Your Infrastructure Affected by CVE-2024-57884?

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

Book a Demo →Browse All CVEs