CVE-2024-41058

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-07-29. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-38858 (ENISA EUVD) · GHSA-77q5-g293-rv7c (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

cachefiles: fix slab-use-after-free in fscache_withdraw_volume()

We got the following issue in our fault injection stress test:

================================================================== BUG: KASAN: slab-use-after-free in fscache_withdraw_volume+0x2e1/0x370 Read of size 4 at addr ffff88810680be08 by task ondemand-04-dae/5798

CPU: 0 PID: 5798 Comm: ondemand-04-dae Not tainted 6.8.0-dirty #565 Call Trace: kasan_check_range+0xf6/0x1b0 fscache_withdraw_volume+0x2e1/0x370 cachefiles_withdraw_volume+0x31/0x50 cachefiles_withdraw_cache+0x3ad/0x900 cachefiles_put_unbind_pincount+0x1f6/0x250 cachefiles_daemon_release+0x13b/0x290 __fput+0x204/0xa00 task_work_run+0x139/0x230

Allocated by task 5820: __kmalloc+0x1df/0x4b0 fscache_alloc_volume+0x70/0x600 __fscache_acquire_volume+0x1c/0x610 erofs_fscache_register_volume+0x96/0x1a0 erofs_fscache_register_fs+0x49a/0x690 erofs_fc_fill_super+0x6c0/0xcc0 vfs_get_super+0xa9/0x140 vfs_get_tree+0x8e/0x300 do_new_mount+0x28c/0x580 [...]

Freed by task 5820: kfree+0xf1/0x2c0 fscache_put_volume.part.0+0x5cb/0x9e0 erofs_fscache_unregister_fs+0x157/0x1b0 erofs_kill_sb+0xd9/0x1c0 deactivate_locked_super+0xa3/0x100 vfs_get_super+0x105/0x140 vfs_get_tree+0x8e/0x300 do_new_mount+0x28c/0x580 [...] ==================================================================

Following is the process that triggers the issue:

mount failed | daemon exit ------------------------------------------------------------ deactivate_locked_super cachefiles_daemon_release erofs_kill_sb erofs_fscache_unregister_fs fscache_relinquish_volume __fscache_relinquish_volume fscache_put_volume(fscache_volume, fscache_volume_put_relinquish) zero = __refcount_dec_and_test(&fscache_volume->ref, &ref); cachefiles_put_unbind_pincount cachefiles_daemon_unbind cachefiles_withdraw_cache cachefiles_withdraw_volumes list_del_init(&volume->cache_link) fscache_free_volume(fscache_volume) cache->ops->free_volume cachefiles_free_volume list_del_init(&cachefiles_volume->cache_link); kfree(fscache_volume) cachefiles_withdraw_volume fscache_withdraw_volume fscache_volume->n_accesses // fscache_volume UAF !!!

The fscache_volume in cache->volumes must not have been freed yet, but its reference count may be 0. So use the new fscache_try_get_volume() helper function try to get its reference count.

If the reference count of fscache_volume is 0, fscache_put_volume() is freeing it, so wait for it to be removed from cache->volumes.

If its reference count is not 0, call cachefiles_withdraw_volume() with reference count protection to avoid the above issue.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
20th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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

July 29, 2024

Last Modified

November 3, 2025

Advisory Details (5)

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

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

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

cachefiles: fix slab-use-after-free in fscache_withdraw_volume() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9dd7f5663899ea13a6a73216106d9c13c37453e3
Web page

cachefiles: fix slab-use-after-free in fscache_withdraw_volume() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90f17e47f1e209c6a3c92a1d038a0a80c95c460e
Web page

cachefiles: fix slab-use-after-free in fscache_withdraw_volume() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/522018a0de6b6fcce60c04f86dfc5f0e4b6a1b36
Web page

cachefiles: fix slab-use-after-free in fscache_withdraw_volume() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38b88d544216f806d93a273a62ff8ebe82254003

Vendor Advisories for CVE-2024-41058(2)

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

Patch Availability(12)

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.99-1 (26 versions)
  • every version up to 6.1.106-1: fixed in 6.1.106-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.11-1: fixed in 6.9.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.11-1: fixed in 6.9.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-41058?
CVE-2024-41058 is a high-severity vulnerability; its CVE record was published on July 29, 2024. In the Linux kernel, the following vulnerability has been resolved: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() We got the following issue in our fault injection stress test: ================================================================== BUG: KASAN: slab-use-after-free in…
When was the CVE record for CVE-2024-41058 published?
The CVE record for CVE-2024-41058 was published on July 29, 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-41058 actively exploited?
CVE-2024-41058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-41058?
CVE-2024-41058 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-41058?
A fix for CVE-2024-41058 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-41058 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-41058

Explore →

Is Your Infrastructure Affected by CVE-2024-41058?

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