Threat Feed

CVE-2026-99513: lockd: Fix use-after-free in nlmsvc_retry_blocked

Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: lockd: Fix use-after-free in nlmsvc_retry_blocked nlmsvc_retry_blocked() examines the block at the head of nlm_blocked under nlm_blocked_lock, then releases the lock before calling nlmsvc_grant_blocked() or retry_deferred_block(). The nlm_blocked list reference is all that keeps the block alive across that window. nlmsvc_grant_blocked() does take one of its own, but not until after the lock has been dropped. Unmounting the nfsd filesystem while a lock request is still blocked reaches nlmsvc_traverse_blocks(), which drops the list reference and frees the block along with the nlm_rqst hanging off it. BUG: KASAN: slab-use-after-free in nlm_async_call+0xd6/0x230 Read of size 8 at addr ffff88811b04c808 by task lockd/8377 nlm_async_call+0xd6/0x230 nlmsvc_retry_blocked+0x61c/0x800 lockd+0x144/0x1c0 Freed by task 8392: nlmsvc_release_block+0x231/0x290 nlmsvc_traverse_blocks+0x139/0x1b0 nlm_traverse_files+0x1aa/0xa00 nlmsvc_free_host_resources+0x12/0x60 nlm_shutdown_hosts_net+0x127/0x280 lockd_down+0xd5/0x1c0 Take a reference before releasing nlm_blocked_lock and drop it once the retry has run.

Enclave's analysis

This is a use-after-free race in the Linux kernel's NFS lock manager (lockd), triggered when something frees a blocked lock request while nlmsvc_retry_blocked() is still using it. NVD scores it 9.8 claiming a pure remote trigger, but the only confirmed path needs an admin to unmount an NFS export while a lock is pending, and the reporter needed artificial delays to hit the race reliably. Red Hat independently scores it 4.1, moderate, DoS-only. Patch to a fixed kernel (6.12.117+, 6.18.61+, or 7.3.2+) to close it.

Fix

Upgrade Linux kernel (fs/lockd/svclock.c, NLM lock manager) to 6.12.117, 6.18.61, 7.3.2, or 7.4-rc1 mainline; Debian kernel package (linux) to 6.12.117-1 / 7.3.4-1 / 7.3.5-1. No fixed version is listed for Linux, Red Hat Enterprise Linux kernel (RHEL 9/10, OpenShift CoreOS); follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
Linux0e4ac9d93515b27fd7635332d73eae3192ed5d4e before 6506c27da6756c0c7590ef60774ee5d35f6a4100Not listed
Linux0e4ac9d93515b27fd7635332d73eae3192ed5d4e before 70825b251e5f7855fd7bd93afc0b698154e00e70Not listed
Linux0e4ac9d93515b27fd7635332d73eae3192ed5d4e before 25d0baa6adb4a0b3f6889d42033ce8df3232bea7Not listed
Linux0e4ac9d93515b27fd7635332d73eae3192ed5d4e before f5b7634f0f213299a07b461fb10385c8639a4ab8Not listed
Linux2.6.22Not listed
Linux kernel (fs/lockd/svclock.c, NLM lock manager)2.6.22 up to (but not including) 6.12.117 / 6.18.61 / 7.3.2 depending on branch; pre-7.4-rc1 mainline6.12.117, 6.18.61, 7.3.2, or 7.4-rc1 mainline
Red Hat Enterprise Linux kernel (RHEL 9/10, OpenShift CoreOS)Vulnerable as of Red Hat's assessment; fix deferred (RHEL 8 not affected, code absent)Not listed
Debian kernel package (linux)bookworm (6.1.x) vulnerable; trixie/forky/sid already fixed6.12.117-1 / 7.3.4-1 / 7.3.5-1

Seen in 2 sources