PT-2026-151724
CVE-2026-99513
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾