CVE-2024-53178

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

Score 4.7 from GitHub Security Advisory published 2024-12-27. NVD baseline CVSS 4.7; 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-51850 (ENISA EUVD) · GHSA-cg3f-qqrv-qxm5 (GitHub Security Advisories)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.5%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

smb: Don't leak cfid when reconnect races with open_cached_dir

open_cached_dir() may either race with the tcon reconnection even before compound_send_recv() or directly trigger a reconnection via SMB2_open_init() or SMB_query_info_init().

The reconnection process invokes invalidate_all_cached_dirs() via cifs_mark_open_files_invalid(), which removes all cfids from the cfids->entries list but doesn't drop a ref if has_lease isn't true. This results in the currently-being-constructed cfid not being on the list, but still having a refcount of 2. It leaks if returned from open_cached_dir().

Fix this by setting cfid->has_lease when the ref is actually taken; the cfid will not be used by other threads until it has a valid time.

Addresses these kmemleaks:

unreferenced object 0xffff8881090c4000 (size 1024): comm "bash", pid 1860, jiffies 4295126592 hex dump (first 32 bytes): 00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de ........"....... 00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff ..E"......O..... backtrace (crc 6f58c20f): [] __kmalloc_cache_noprof+0x2be/0x350 [] open_cached_dir+0x993/0x1fb0 [] cifs_readdir+0x15a0/0x1d50 [] iterate_dir+0x28f/0x4b0 [] __x64_sys_getdents64+0xfd/0x200 [] do_syscall_64+0x95/0x1a0 [] entry_SYSCALL_64_after_hwframe+0x76/0x7e unreferenced object 0xffff8881044fdcf8 (size 8): comm "bash", pid 1860, jiffies 4295126592 hex dump (first 8 bytes): 00 cc cc cc cc cc cc cc ........ backtrace (crc 10c106a9): [] __kmalloc_node_track_caller_noprof+0x363/0x480 [] kstrdup+0x36/0x60 [] open_cached_dir+0x9b0/0x1fb0 [] cifs_readdir+0x15a0/0x1d50 [] iterate_dir+0x28f/0x4b0 [] __x64_sys_getdents64+0xfd/0x200 [] do_syscall_64+0x95/0x1a0 [] entry_SYSCALL_64_after_hwframe+0x76/0x7e

And addresses these BUG splats when unmounting the SMB filesystem:

BUG: Dentry ffff888140590ba0{i=1000000000080,n=/} still in use (2) [unmount of cifs cifs] WARNING: CPU: 3 PID: 3433 at fs/dcache.c:1536 umount_check+0xd0/0x100 Modules linked in: CPU: 3 UID: 0 PID: 3433 Comm: bash Not tainted 6.12.0-rc4-g850925a8133c-dirty #49 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 RIP: 0010:umount_check+0xd0/0x100 Code: 8d 7c 24 40 e8 31 5a f4 ff 49 8b 54 24 40 41 56 49 89 e9 45 89 e8 48 89 d9 41 57 48 89 de 48 c7 c7 80 e7 db ac e8 f0 72 9a ff <0f> 0b 58 31 c0 5a 5b 5d 41 5c 41 5d 41 5e 41 5f e9 2b e5 5d 01 41 RSP: 0018:ffff88811cc27978 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff888140590ba0 RCX: ffffffffaaf20bae RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8881f6fb6f40 RBP: ffff8881462ec000 R08: 0000000000000001 R09: ffffed1023984ee3 R10: ffff88811cc2771f R11: 00000000016cfcc0 R12: ffff888134383e08 R13: 0000000000000002 R14: ffff8881462ec668 R15: ffffffffaceab4c0 FS: 00007f23bfa98740(0000) GS:ffff8881f6f80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556de4a6f808 CR3: 0000000123c80000 CR4: 0000000000350ef0 Call Trace: d_walk+0x6a/0x530 shrink_dcache_for_umount+0x6a/0x200 generic_shutdown_super+0x52/0x2a0 kill_anon_super+0x22/0x40 cifs_kill_sb+0x159/0x1e0 deactivate_locked_super+0x66/0xe0 cleanup_mnt+0x140/0x210 task_work_run+0xfb/0x170 syscall_exit_to_user_mode+0x29f/0x2b0 do_syscall_64+0xa1/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f23bfb93ae7 Code: ff ff ff ff c3 66 0f 1f 44 00 00 48 8b 0d 11 93 0d 00 f7 d8 64 89 01 b8 ff ff ff ff eb bf 0f 1f 44 00 00 b8 50 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e9 92 0d 00 f7 d8 64 89 ---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.5% × 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.5%
EPSS %ILE
45th
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.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

December 27, 2024

Last Modified

October 30, 2026

References (5)

Vendor Advisories for CVE-2024-53178(1)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-30ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-30ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-10-30ubuntu
linuxKernel @ 6.6.64 (fixes >=6.1.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.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 44× 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 216 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 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53178?
CVE-2024-53178 is a medium-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: smb: Don't leak cfid when reconnect races with open_cached_dir open_cached_dir() may either race with the tcon reconnection even before compound_send_recv() or directly trigger a reconnection via SMB2_open_init() or…
When was the CVE record for CVE-2024-53178 published?
The CVE record for CVE-2024-53178 was published on December 27, 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2024-53178 actively exploited?
CVE-2024-53178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53178?
CVE-2024-53178 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-53178?
A fix for CVE-2024-53178 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53178 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-53178

Explore →

Is Your Infrastructure Affected by CVE-2024-53178?

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

Book a Demo →Browse All CVEs