PT-2026-151559
CVE-2026-99378
·
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:
pnfs/blocklayout: Complete a device upcall when the pipe is closed
Once blkmapd has read a whole upcall, rpc pipe read() unlinks the
message from every pipe list, so the purges in rpc pipe release()
and rpc close pipes() no longer reach it. bl upcall ops supplies no
.release pipe callback, and bl pipe destroy msg() returns without
completing the upcall because a downcall is expected to follow. A
daemon that exits between the read and the write therefore strands
its waiter: bl resolve deviceid() sleeps in wait for completion()
and never returns, and it holds nn->bl mutex across that wait, so
every later device resolution in the net namespace blocks behind
it.
Add a .release pipe that completes an upcall blkmapd has consumed
and left unanswered. Completing an upcall retires it, so a message
the framework has already purged is no longer in flight and is not
completed a second time here.
Found an issue in the description? Have something to add? Feel free to write us 👾