CVE-2024-45000

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-09-04. 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-41571 (ENISA EUVD) · GHSA-gcpr-pgrp-45fp (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:

fs/netfs/fscache_cookie: add missing "n_accesses" check

This fixes a NULL pointer dereference bug due to a data race which looks like this:

BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP PTI CPU: 33 PID: 16573 Comm: kworker/u97:799 Not tainted 6.8.7-cm4all1-hp+ #43 Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/17/2018 Workqueue: events_unbound netfs_rreq_write_to_cache_work RIP: 0010:cachefiles_prepare_write+0x30/0xa0 Code: 57 41 56 45 89 ce 41 55 49 89 cd 41 54 49 89 d4 55 53 48 89 fb 48 83 ec 08 48 8b 47 08 48 83 7f 10 00 48 89 34 24 48 8b 68 20 <48> 8b 45 08 4c 8b 38 74 45 49 8b 7f 50 e8 4e a9 b0 ff 48 8b 73 10 RSP: 0018:ffffb4e78113bde0 EFLAGS: 00010286 RAX: ffff976126be6d10 RBX: ffff97615cdb8438 RCX: 0000000000020000 RDX: ffff97605e6c4c68 RSI: ffff97605e6c4c60 RDI: ffff97615cdb8438 RBP: 0000000000000000 R08: 0000000000278333 R09: 0000000000000001 R10: ffff97605e6c4600 R11: 0000000000000001 R12: ffff97605e6c4c68 R13: 0000000000020000 R14: 0000000000000001 R15: ffff976064fe2c00 FS: 0000000000000000(0000) GS:ffff9776dfd40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 000000005942c002 CR4: 00000000001706f0 Call Trace: ? __die+0x1f/0x70 ? page_fault_oops+0x15d/0x440 ? search_module_extables+0xe/0x40 ? fixup_exception+0x22/0x2f0 ? exc_page_fault+0x5f/0x100 ? asm_exc_page_fault+0x22/0x30 ? cachefiles_prepare_write+0x30/0xa0 netfs_rreq_write_to_cache_work+0x135/0x2e0 process_one_work+0x137/0x2c0 worker_thread+0x2e9/0x400 ? __pfx_worker_thread+0x10/0x10 kthread+0xcc/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 Modules linked in: CR2: 0000000000000008 ---[ end trace 0000000000000000 ]---

This happened because fscache_cookie_state_machine() was slow and was still running while another process invoked fscache_unuse_cookie(); this led to a fscache_cookie_lru_do_one() call, setting the FSCACHE_COOKIE_DO_LRU_DISCARD flag, which was picked up by fscache_cookie_state_machine(), withdrawing the cookie via cachefiles_withdraw_cookie(), clearing cookie->cache_priv.

At the same time, yet another process invoked cachefiles_prepare_write(), which found a NULL pointer in this code line:

struct cachefiles_object *object = cachefiles_cres_object(cres);

The next line crashes, obviously:

struct cachefiles_cache *cache = object->volume->cache;

During cachefiles_prepare_write(), the "n_accesses" counter is non-zero (via fscache_begin_operation()). The cookie must not be withdrawn until it drops to zero.

The counter is checked by fscache_cookie_state_machine() before switching to FSCACHE_COOKIE_STATE_RELINQUISHING and FSCACHE_COOKIE_STATE_WITHDRAWING (in "case FSCACHE_COOKIE_STATE_FAILED"), but not for FSCACHE_COOKIE_STATE_LRU_DISCARDING ("case FSCACHE_COOKIE_STATE_ACTIVE").

This patch adds the missing check. With a non-zero access counter, the function returns and the next fscache_end_cookie_access() call will queue another fscache_cookie_state_machine() call to handle the still-pending FSCACHE_COOKIE_DO_LRU_DISCARD.

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
14th
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 (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

September 4, 2024

Last Modified

August 5, 2026

Vendor Advisories for CVE-2024-45000(2)

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-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.1.107 (fixes >=5.17.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.106-1 ... 6.1.99-1 (29 versions)
  • every version up to 6.1.112-1: fixed in 6.1.112-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.7-1: fixed in 6.10.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.7-1: fixed in 6.10.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-45000?
CVE-2024-45000 is a medium-severity vulnerability; its CVE record was published on September 4, 2024. In the Linux kernel, the following vulnerability has been resolved: fs/netfs/fscache_cookie: add missing "n_accesses" check This fixes a NULL pointer dereference bug due to a data race which looks like this: BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor read access…
When was the CVE record for CVE-2024-45000 published?
The CVE record for CVE-2024-45000 was published on September 4, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-45000 actively exploited?
CVE-2024-45000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45000?
CVE-2024-45000 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-45000?
A fix for CVE-2024-45000 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-45000 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-45000

Explore →

Is Your Infrastructure Affected by CVE-2024-45000?

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