CVE-2024-53216

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
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nfsd: release svc_expkey/svc_export with rcu_work

The last reference for cache_head can be reduced to zero in c_show and e_show(using rcu_read_lock and rcu_read_unlock). Consequently, svc_export_put and expkey_put will be invoked, leading to two issues:

  • The svc_export_put will directly free ex_uuid. However,
e_show/c_show will access ex_uuid after cache_put, which can trigger a use-after-free issue, shown below.

================================================================== BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd] Read of size 1 at addr ff11000010fdc120 by task cat/870

CPU: 1 UID: 0 PID: 870 Comm: cat Not tainted 6.12.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: dump_stack_lvl+0x53/0x70 print_address_description.constprop.0+0x2c/0x3a0 print_report+0xb9/0x280 kasan_report+0xae/0xe0 svc_export_show+0x362/0x430 [nfsd] c_show+0x161/0x390 [sunrpc] seq_read_iter+0x589/0x770 seq_read+0x1e5/0x270 proc_reg_read+0xe1/0x140 vfs_read+0x125/0x530 ksys_read+0xc1/0x160 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Allocated by task 830: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 __kmalloc_node_track_caller_noprof+0x1bc/0x400 kmemdup_noprof+0x22/0x50 svc_export_parse+0x8a9/0xb80 [nfsd] cache_do_downcall+0x71/0xa0 [sunrpc] cache_write_procfs+0x8e/0xd0 [sunrpc] proc_reg_write+0xe1/0x140 vfs_write+0x1a5/0x6d0 ksys_write+0xc1/0x160 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Freed by task 868: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x37/0x50 kfree+0xf3/0x3e0 svc_export_put+0x87/0xb0 [nfsd] cache_purge+0x17f/0x1f0 [sunrpc] nfsd_destroy_serv+0x226/0x2d0 [nfsd] nfsd_svc+0x125/0x1e0 [nfsd] write_threads+0x16a/0x2a0 [nfsd] nfsctl_transaction_write+0x74/0xa0 [nfsd] vfs_write+0x1a5/0x6d0 ksys_write+0xc1/0x160 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e

  • We cannot sleep while using rcu_read_lock/rcu_read_unlock.
However, svc_export_put/expkey_put will call path_put, which subsequently triggers a sleeping operation due to the following dput.

============================= WARNING: suspicious RCU usage 5.10.0-dirty #141 Not tainted ----------------------------- ... Call Trace: dump_stack+0x9a/0xd0 ___might_sleep+0x231/0x240 dput+0x39/0x600 path_put+0x1b/0x30 svc_export_put+0x17/0x80 e_show+0x1c9/0x200 seq_read_iter+0x63f/0x7c0 seq_read+0x226/0x2d0 vfs_read+0x113/0x2c0 ksys_read+0xc9/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x67/0xd1

Fix these issues by using rcu_work to help release svc_expkey/svc_export. This approach allows for an asynchronous context to invoke path_put and also facilitates the freeing of uuid/exp/key after an RCU grace period.

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 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)
Severity78% × 45%
The EG Score, 7.8 of 10.
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 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.2%
EPSS %ILE
11th
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

December 27, 2024

Last Modified

August 5, 2026

Advisory Details (4)

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

nfsd: release svc_expkey/svc_export with rcu_work - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: release svc_expkey/svc_export with rcu_work - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: release svc_expkey/svc_export with rcu_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e4854599200f4d021df8ae17e69221d7c149f3e
Web page

nfsd: release svc_expkey/svc_export with rcu_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bd8524148dd8c123334b066faa90590ba2ef8e6f

Vendor Advisories for CVE-2024-53216(4)

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-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
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
redhatkernel-0:5.14.0-570.112.1.el9_62026-05-06redhat
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.6.64 (fixes >=4.20.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
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53216?
CVE-2024-53216 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: nfsd: release svcexpkey/svcexport with rcu_work The last reference for cachehead can be reduced to zero in cshow and eshow(using rcureadlock and rcuread_unlock). Consequently, svcexportput and expkey_put will be invoked, leading to…
When was the CVE record for CVE-2024-53216 published?
The CVE record for CVE-2024-53216 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-53216 actively exploited?
CVE-2024-53216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53216?
CVE-2024-53216 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53216?
A fix for CVE-2024-53216 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53216 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-53216

Explore →

Is Your Infrastructure Affected by CVE-2024-53216?

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

Book a Demo →Browse All CVEs