CVE-2024-50121

nfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net

HIGH
7.8
CVSS Score
Published: November 5, 2024 at 05:10 PM UTC
Updated: October 15, 2026 at 01:19 AM UTC
2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net In the normal case, when we excute `echo 0 > /proc/fs/nfsd/threads`, the function `nfs4_state_destroy_net` in `nfs4_state_shutdown_net` will release all resources related to the hashed `nfs4_client`. If the `nfsd_client_shrinker` is running concurrently, the `expire_client` function will first unhash this client and then destroy it. This can lead to the following warning. Additionally, numerous use-after-free errors may occur as well. nfsd_client_shrinker echo 0 > /proc/fs/nfsd/threads expire_client nfsd_shutdown_net unhash_client ... nfs4_state_shutdown_net /* won't wait shrinker exit */ /* cancel_work(&nn->nfsd_shrinker_work) * nfsd_file for this /* won't destroy unhashed client1 */ * client1 still alive nfs4_state_destroy_net */ nfsd_file_cache_shutdown /* trigger warning */ kmem_cache_destroy(nfsd_file_slab) kmem_cache_destroy(nfsd_file_mark_slab) /* release nfsd_file and mark */ __destroy_client ==================================================================== BUG nfsd_file (Not tainted): Objects remaining in nfsd_file on __kmem_cache_shutdown() -------------------------------------------------------------------- CPU: 4 UID: 0 PID: 764 Comm: sh Not tainted 6.12.0-rc3+ #1 dump_stack_lvl+0x53/0x70 slab_err+0xb0/0xf0 __kmem_cache_shutdown+0x15c/0x310 kmem_cache_destroy+0x66/0x160 nfsd_file_cache_shutdown+0xac/0x210 [nfsd] nfsd_destroy_serv+0x251/0x2a0 [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 ==================================================================== BUG nfsd_file_mark (Tainted: G B W ): Objects remaining nfsd_file_mark on __kmem_cache_shutdown() -------------------------------------------------------------------- dump_stack_lvl+0x53/0x70 slab_err+0xb0/0xf0 __kmem_cache_shutdown+0x15c/0x310 kmem_cache_destroy+0x66/0x160 nfsd_file_cache_shutdown+0xc8/0x210 [nfsd] nfsd_destroy_serv+0x251/0x2a0 [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 To resolve this issue, cancel `nfsd_shrinker_work` using synchronous mode in nfs4_state_shutdown_net.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.220 ≤ v < 5.155.15.154 ≤ v < 6.16.2 ≤ v < 6.6.596.7 ≤ v < 6.11.62bbf10861d51dae76c6da7113516d0071c7826535.10.2205.15.1546.1.816.126.12 rc16.12 rc26.12 rc36.12 rc47c24fa225081f31bc6da6a355c1ba801889ab29a958294a3eb82026fcfff20b0287a90e9c854785ef3ea5ec83d1a827f074b2b660749817e0bf2b23e
Vendor states this is fixed in 36775f42e039b01d4abe8998bf66771a37d3cdcc (fixed)
Vendor states this is fixed in 5ade4382de16c34d9259cb548f36ec5c4555913c (fixed)
Vendor states this is fixed in add1df5eba163a3a6ece11cb85890e2e410baaea (fixed)
Vendor states this is fixed in d5ff2fb2e7167e9483846e34148e60c0c016a1f6 (fixed)
Vendor states this is fixed in f67138dd338cb564ade7d3755c8cd4f68b46d397 (fixed)
Vendor states this is fixed in f965dc0f099a54fca100acf6909abe52d0c85328 (fixed)
Vendor states this is fixed in 5.10.233 (unaffected)
Affected range stops below 5.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15.176 (unaffected)
Affected range stops below 6.1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.123 (unaffected)
Vendor states this is fixed in 6.11.6 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.59 (unaffected)

References (9)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card