LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54269: SUNRPC: double free xprt_ctxt while still in use

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-54269 is a Linux kernel SUNRPC bug where a transport context can be freed twice after repeated request deferral. The source describes a likely kernel oops, which means service disruption or system instability is the main documented impact. No CVSS score or active exploitation evidence is provided.

Executive priority

Treat as a focused kernel maintenance issue, not an emergency based on current evidence. Prioritize patch verification on RPC-exposed Linux servers, especially where outages would affect critical operations.

Technical view

In SUNRPC, rq_xprt_ctxt moves from svc_rqst to svc_deferred_req during deferral. When revisited and deferred again, the stale pointer may remain and be released, then later reused and freed again. The kernel fix clears rq_xprt_ctxt in svc_defer() and asserts the context is stored in the deferred request.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with SUNRPC service paths in use. The source bundle lists Linux kernel versions and stable commits, but does not identify distributions, appliances, or default service exposure.

Exploitation context

The bundle does not report active exploitation, and KEV is false. It describes a rare second-deferral condition that may lead to invalid memory reference and kernel oops. No public exploit details are included in the provided sources.

Researcher notes

The record lacks CVSS, CWE mapping, distribution impact, and exploit evidence. Analysis should center on commit presence and kernel provenance, because downstream vendors may backport the fix without matching upstream version numbers.

Mitigation direction

  • Identify Linux kernel versions across servers and appliances.
  • Compare running kernels with vendor advisories and kernel stable fixes.
  • Prioritize systems using SUNRPC-dependent services or exposing RPC to untrusted networks.
  • Apply distribution or vendor kernel updates when available.
  • Restrict RPC exposure where business operations allow.

Validation and detection

  • Check whether assets run Linux kernel versions listed as affected.
  • Confirm installed kernel includes the referenced stable fix commits.
  • Review vendor advisories for backported fixes using different version numbers.
  • Verify SUNRPC-related services are required and appropriately network-restricted.
  • Monitor kernel logs for RPC-related oops or crash indicators.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54269 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf5e13d700a4d40ccde3d36e383f9247dcb3c1d2d, 773f91b2cf3f52df0d7508fdbf60f37567cdaee4, 773f91b2cf3f52df0d7508fdbf60f37567cdaee4, 773f91b2cf3f52df0d7508fdbf60f37567cdaee4, 11fab500f86403b2ebf6795feeade6e10302e448, 5.15.35, 5.17.4unaffected
LinuxLinux5.18, 0, 5.15.113, 6.1.30, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.