Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-53216: nfsd: release svc_expkey/svc_export with rcu_work

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2e4854599200f4d021df8ae17e69221d7c149f3e, a98fa661769edacd3bf319c4a150f00bea61945b, ad4363a24a5746b257c0beb5d8cc68f9b62c173f.

Low priority for now. Upgrade to Linux Linux 2e4854599200f4d021df8ae17e69221d7c149f3e, a98fa661769edacd3bf319c4a150f00bea61945b, ad4363a24a5746b257c0beb5d8cc68f9b62c173f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: 1. 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: <TASK> 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 2. 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.

Published
Dec 27, 2024
Updated
Oct 30, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-53216

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.20affected
    • 9ceddd9da13434a5906255c0fc528c385aded283 and later · before a98fa661769edacd3bf319c4a150f00bea61945baffected · git
    • 9ceddd9da13434a5906255c0fc528c385aded283 and later · before bd8524148dd8c123334b066faa90590ba2ef8e6faffected · git
    • 9ceddd9da13434a5906255c0fc528c385aded283 and later · before 2e4854599200f4d021df8ae17e69221d7c149f3eaffected · git
    • 9ceddd9da13434a5906255c0fc528c385aded283 and later · before ad4363a24a5746b257c0beb5d8cc68f9b62c173faffected · git
    • 9ceddd9da13434a5906255c0fc528c385aded283 and later · before f8c989a0c89a75d30f899a7cabdc14d72522bb8daffected · git
    • before 4.20not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.64 and later · up to and including 6.6.*not affected · semver
    • 6.11.11 and later · up to and including 6.11.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.20 and later · before 6.6.64
  • linux linux kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64kbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debugbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-cross-headersbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debugbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-develbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-124.8.1.el10_16.12.0-124.8.1.el10_1

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-53201Dec 27, 2024 · drm/amd/display: Fix null check for pipe_ctx->plane_state in dcn20_program_pipe
    22Monitor
  • ← EarlierCVE-2024-53209Dec 27, 2024 · bnxt_en: Fix receive ring space parameters when XDP is active
    22Monitor
  • Later →CVE-2024-53217Dec 27, 2024 · NFSD: Prevent NULL dereference in nfsd4_process_cb_update()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2e4854599200f4d021df8ae17e69221d7c149f3eVendor (CNA)
Linux Linuxa98fa661769edacd3bf319c4a150f00bea61945bVendor (CNA)
Linux Linuxad4363a24a5746b257c0beb5d8cc68f9b62c173fVendor (CNA)
Linux Linuxbd8524148dd8c123334b066faa90590ba2ef8e6fVendor (CNA)
Linux Linuxf8c989a0c89a75d30f899a7cabdc14d72522bb8dVendor (CNA)
almalinux:kernel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-124.8.1.el10_1 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.3-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records