All reports
Medium

kernel: SUNRPC: double free xprt_ctxt while still in use

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-54269

Probability of exploitation in the next 30 days: 0.55%

FIRST EPSS · 2026-11-18

Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: double free xprt_ctxt while still in use When an RPC request is deferred, the rq_xprt_ctxt pointer is moved out of the svc_rqst into the svc_deferred_req. When the deferred request is revisited, the pointer is copied into the new svc_rqst - and also remains in the svc_deferred_req. In the (rare?) case that the request is deferred a second time, the old svc_deferred_req is reused - it still has all the correct content. However in that case the rq_xprt_ctxt pointer is NOT cleared so that when xpo_release_xprt is called, the ctxt is freed (UDP) or possible added to a free list (RDMA). When the deferred request is revisited for a second time, it will reference this ctxt which may be invalid, and the free the object a second time which is likely to oops. So change svc_defer() to always clear rq_xprt_ctxt, and assert that the value is now stored in the svc_deferred_req.

A flaw was addressed in the Linux kernel’s SUNRPC implementation affecting deferred RPC request handling. When an RPC request is deferred, the internal rq_xprt_ctxt pointer is moved from the active service request to a deferred request structure. Under certain rare conditions where a request is deferred multiple times, the old context pointer is not cleared before reuse. This can lead to the context being freed twice while still referenced, causing memory corruption and likely resulting in a kernel oops/crash