CVE-2024-50106

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2024-11-05. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.0EG
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.5%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nfsd: fix race between laundromat and free_stateid

There is a race between laundromat handling of revoked delegations and a client sending free_stateid operation. Laundromat thread finds that delegation has expired and needs to be revoked so it marks the delegation stid revoked and it puts it on a reaper list but then it unlock the state lock and the actual delegation revocation happens without the lock. Once the stid is marked revoked a racing free_stateid processing thread does the following (1) it calls list_del_init() which removes it from the reaper list and (2) frees the delegation stid structure. The laundromat thread ends up not calling the revoke_delegation() function for this particular delegation but that means it will no release the lock lease that exists on the file.

Now, a new open for this file comes in and ends up finding that lease list isn't empty and calls nfsd_breaker_owns_lease() which ends up trying to derefence a freed delegation stateid. Leading to the followint use-after-free KASAN warning:

kernel: ================================================================== kernel: BUG: KASAN: slab-use-after-free in nfsd_breaker_owns_lease+0x140/0x160 [nfsd] kernel: Read of size 8 at addr ffff0000e73cd0c8 by task nfsd/6205 kernel: kernel: CPU: 2 UID: 0 PID: 6205 Comm: nfsd Kdump: loaded Not tainted 6.11.0-rc7+ #9 kernel: Hardware name: Apple Inc. Apple Virtualization Generic Platform, BIOS 2069.0.0.0.0 08/03/2024 kernel: Call trace: kernel: dump_backtrace+0x98/0x120 kernel: show_stack+0x1c/0x30 kernel: dump_stack_lvl+0x80/0xe8 kernel: print_address_description.constprop.0+0x84/0x390 kernel: print_report+0xa4/0x268 kernel: kasan_report+0xb4/0xf8 kernel: __asan_report_load8_noabort+0x1c/0x28 kernel: nfsd_breaker_owns_lease+0x140/0x160 [nfsd] kernel: nfsd_file_do_acquire+0xb3c/0x11d0 [nfsd] kernel: nfsd_file_acquire_opened+0x84/0x110 [nfsd] kernel: nfs4_get_vfs_file+0x634/0x958 [nfsd] kernel: nfsd4_process_open2+0xa40/0x1a40 [nfsd] kernel: nfsd4_open+0xa08/0xe80 [nfsd] kernel: nfsd4_proc_compound+0xb8c/0x2130 [nfsd] kernel: nfsd_dispatch+0x22c/0x718 [nfsd] kernel: svc_process_common+0x8e8/0x1960 [sunrpc] kernel: svc_process+0x3d4/0x7e0 [sunrpc] kernel: svc_handle_xprt+0x828/0xe10 [sunrpc] kernel: svc_recv+0x2cc/0x6a8 [sunrpc] kernel: nfsd+0x270/0x400 [nfsd] kernel: kthread+0x288/0x310 kernel: ret_from_fork+0x10/0x20

This patch proposes a fixed that's based on adding 2 new additional stid's sc_status values that help coordinate between the laundromat and other operations (nfsd4_free_stateid() and nfsd4_delegreturn()).

First to make sure, that once the stid is marked revoked, it is not removed by the nfsd4_free_stateid(), the laundromat take a reference on the stateid. Then, coordinating whether the stid has been put on the cl_revoked list or we are processing FREE_STATEID and need to make sure to remove it from the list, each check that state and act accordingly. If laundromat has added to the cl_revoke list before the arrival of FREE_STATEID, then nfsd4_free_stateid() knows to remove it from the list. If nfsd4_free_stateid() finds that operations arrived before laundromat has placed it on cl_revoke list, it marks the state freed and then laundromat will no longer add it to the list.

Also, for nfsd4_delegreturn() when looking for the specified stid, we need to access stid that are marked removed or freeable, it means the laundromat has started processing it but hasn't finished and this delegreturn needs to return nfserr_deleg_revoked and not nfserr_bad_stateid. The latter will not trigger a FREE_STATEID and the lack of it will leave this stid on the cl_revoked list indefinitely.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
The EG Score, 7.0 of 10.
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.5%
EPSS %ILE
41st
KEV
Not listed

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.

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

November 5, 2024

Last Modified

August 5, 2026

References (2)

Vendor Advisories for CVE-2024-50106(2)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.11.6 (fixes >=6.9.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.11.6-1: fixed in 6.11.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 10× in last 7d / 32× 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 91 of 190 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-50106?
CVE-2024-50106 is a high-severity vulnerability; its CVE record was published on November 5, 2024. In the Linux kernel, the following vulnerability has been resolved: nfsd: fix race between laundromat and free_stateid There is a race between laundromat handling of revoked delegations and a client sending free_stateid operation. Laundromat thread finds that delegation has expired and needs to be…
When was the CVE record for CVE-2024-50106 published?
The CVE record for CVE-2024-50106 was published on November 5, 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-50106 actively exploited?
CVE-2024-50106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50106?
CVE-2024-50106 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2024-50106?
A fix for CVE-2024-50106 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50106 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-50106

Explore →

Is Your Infrastructure Affected by CVE-2024-50106?

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

Book a Demo →Browse All CVEs