CVE-2024-53177

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-12-27. 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-51849 (ENISA EUVD) · GHSA-5hh7-6vv2-v2hg (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.6%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

smb: prevent use-after-free due to open_cached_dir error paths

If open_cached_dir() encounters an error parsing the lease from the server, the error handling may race with receiving a lease break, resulting in open_cached_dir() freeing the cfid while the queued work is pending.

Update open_cached_dir() to drop refs rather than directly freeing the cfid.

Have cached_dir_lease_break(), cfids_laundromat_worker(), and invalidate_all_cached_dirs() clear has_lease immediately while still holding cfids->cfid_list_lock, and then use this to also simplify the reference counting in cfids_laundromat_worker() and invalidate_all_cached_dirs().

Fixes this KASAN splat (which manually injects an error and lease break in open_cached_dir()):

================================================================== BUG: KASAN: slab-use-after-free in smb2_cached_lease_break+0x27/0xb0 Read of size 8 at addr ffff88811cc24c10 by task kworker/3:1/65

CPU: 3 UID: 0 PID: 65 Comm: kworker/3:1 Not tainted 6.12.0-rc6-g255cf264e6e5-dirty #87 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Workqueue: cifsiod smb2_cached_lease_break Call Trace: dump_stack_lvl+0x77/0xb0 print_report+0xce/0x660 kasan_report+0xd3/0x110 smb2_cached_lease_break+0x27/0xb0 process_one_work+0x50a/0xc50 worker_thread+0x2ba/0x530 kthread+0x17c/0x1c0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30

Allocated by task 2464: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 open_cached_dir+0xa7d/0x1fb0 smb2_query_path_info+0x43c/0x6e0 cifs_get_fattr+0x346/0xf10 cifs_get_inode_info+0x157/0x210 cifs_revalidate_dentry_attr+0x2d1/0x460 cifs_getattr+0x173/0x470 vfs_statx_path+0x10f/0x160 vfs_statx+0xe9/0x150 vfs_fstatat+0x5e/0xc0 __do_sys_newfstatat+0x91/0xf0 do_syscall_64+0x95/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Freed by task 2464: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x51/0x70 kfree+0x174/0x520 open_cached_dir+0x97f/0x1fb0 smb2_query_path_info+0x43c/0x6e0 cifs_get_fattr+0x346/0xf10 cifs_get_inode_info+0x157/0x210 cifs_revalidate_dentry_attr+0x2d1/0x460 cifs_getattr+0x173/0x470 vfs_statx_path+0x10f/0x160 vfs_statx+0xe9/0x150 vfs_fstatat+0x5e/0xc0 __do_sys_newfstatat+0x91/0xf0 do_syscall_64+0x95/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Last potentially related work creation: kasan_save_stack+0x33/0x60 __kasan_record_aux_stack+0xad/0xc0 insert_work+0x32/0x100 __queue_work+0x5c9/0x870 queue_work_on+0x82/0x90 open_cached_dir+0x1369/0x1fb0 smb2_query_path_info+0x43c/0x6e0 cifs_get_fattr+0x346/0xf10 cifs_get_inode_info+0x157/0x210 cifs_revalidate_dentry_attr+0x2d1/0x460 cifs_getattr+0x173/0x470 vfs_statx_path+0x10f/0x160 vfs_statx+0xe9/0x150 vfs_fstatat+0x5e/0xc0 __do_sys_newfstatat+0x91/0xf0 do_syscall_64+0x95/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The buggy address belongs to the object at ffff88811cc24c00 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 16 bytes inside of freed 1024-byte region [ffff88811cc24c00, ffff88811cc25000)

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.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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.6%
EPSS %ILE
46th
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.6% 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 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

Advisory Details (4)

Auto-updated Aug 5, 2026
Patch available.
Web page

smb: prevent use-after-free due to open_cached_dir error paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: prevent use-after-free due to open_cached_dir error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47655a12c6b1bca8fa230085eab2e85a076932b7
Web page

smb: prevent use-after-free due to open_cached_dir error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97e2afcac0bebfef6a5360f4267ce4c44507b845
Web page

smb: prevent use-after-free due to open_cached_dir error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/791f833053578b9fd24252ebb7162a61bc3f805b

Vendor Advisories for CVE-2024-53177(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-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-27ubuntu
linuxKernel @ 6.6.64 (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

(2 across 2 ecosystems)
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.

Additional Vendor Advisories

(12)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53177?
CVE-2024-53177 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: smb: prevent use-after-free due to open_cached_dir error paths If open_cached_dir() encounters an error parsing the lease from the server, the error handling may race with receiving a lease break, resulting in open_cached_dir()…
When was the CVE record for CVE-2024-53177 published?
The CVE record for CVE-2024-53177 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-53177 actively exploited?
CVE-2024-53177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53177?
CVE-2024-53177 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53177?
A fix for CVE-2024-53177 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53177 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-53177

Explore →

Is Your Infrastructure Affected by CVE-2024-53177?

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

Book a Demo →Browse All CVEs