CVE-2026-99378: Linux kernel · pnfs/blocklayout: Complete a device upcall when the pipe is closed
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e4db79581b42ced776b726587571969aac162c74 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e4db79581b42ced776b726587571969aac162c74, 9b89bd161183277fe08077f7877b495ec53a2440, 2a25cc8e984610828a526086313b8a7aeefe507d +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to e4db79581b42ced776b726587571969aac162c74, 9b89bd161183277fe08077f7877b495ec53a2440, 2a25cc8e984610828a526086313b8a7aeefe507d or 1c46038a0117c4495783edc8a7532dbda7828e49.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/e4db79581b42ced776b726587571969aac162c74 (opens in a new tab)
- git.kernel.org/stable/c/9b89bd161183277fe08077f7877b495ec53a2440 (opens in a new tab)
- git.kernel.org/stable/c/1c46038a0117c4495783edc8a7532dbda7828e49 (opens in a new tab)
- git.kernel.org/stable/c/2a25cc8e984610828a526086313b8a7aeefe507d (opens in a new tab)