Bug 2576745 (CVE-2026-99378) - CVE-2026-99378 kernel: kernel: Denial of Service via uncompleted upcall in pNFS block layout
Summary: CVE-2026-99378 kernel: kernel: Denial of Service via uncompleted upcall in pN...
Keywords:
Status: NEW
Alias: CVE-2026-99378
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 14:39 UTC by OSIDB Bzimport
Modified: 2026-11-19 18:56 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-19 14:39:28 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.