CVE-2023-54269

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-30. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

SUNRPC: double free xprt_ctxt while still in use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb8d3a2c809abd73ab0a060fe971d6b9019aa3c1
generic

SUNRPC: double free xprt_ctxt while still in use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e0c648627322a4c7e018e5c7f837c3c03e297dbb
generic

SUNRPC: double free xprt_ctxt while still in use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd86534872f445f54dc01e7db001e25eadf063a8
generic

SUNRPC: double free xprt_ctxt while still in use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7851771789e87108a92697194105ef0c9307dc5e

Vendor Advisories for CVE-2023-54269(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatubi8/go-toolset:1.21.13-1.17271729952024-09-26redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.15.113—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-16.1.37-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.3.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.3.7-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 198 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:58 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:34 UTCEPSS rescore
  10. 2026-09-08 21:58 UTCEPSS rescore
  11. 2026-09-07 15:59 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-05 15:26 UTCEPSS rescore
  14. 2026-09-04 13:58 UTCEPSS rescore
  15. 2026-09-04 05:04 UTCEPSS rescore
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-01 13:52 UTCEPSS rescore
  18. 2026-09-01 04:36 UTCEPSS rescore
  19. 2026-09-01 01:04 UTCOSV refresh
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:17 UTCEPSS rescore
  2. 2026-08-23 00:17 UTCEPSS rescore
  3. 2026-08-21 23:47 UTCEPSS rescore
  4. 2026-08-20 22:53 UTCEPSS rescore
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 13:46 UTCEPSS rescore
  7. 2026-08-16 14:54 UTCEPSS rescore
  8. 2026-08-16 02:12 UTCEPSS rescore
  9. 2026-08-15 01:28 UTCEPSS rescore
  10. 2026-08-15 01:03 UTCEG score recompute
  11. 2026-08-15 01:03 UTCVendor advisory
  12. 2026-08-15 01:03 UTCGHSA enrichment
  13. 2026-08-13 21:58 UTCEPSS rescore
  14. 2026-08-12 13:49 UTCEPSS rescore
  15. 2026-08-11 13:40 UTCEPSS rescore
  16. 2026-08-10 23:58 UTCEPSS rescore
  17. 2026-08-09 22:21 UTCEG score recompute
  18. 2026-08-09 22:21 UTCVendor advisory
  19. 2026-08-09 22:21 UTCGHSA enrichment
  20. 2026-08-09 13:44 UTCEPSS rescore
  21. 2026-08-08 16:35 UTCEPSS rescore
  22. 2026-08-08 08:43 UTCVendor advisory
  23. 2026-08-08 08:43 UTCGHSA enrichment
  24. 2026-08-08 04:33 UTCEG score recompute
  25. 2026-08-08 04:33 UTCVendor advisory
  26. 2026-08-08 04:33 UTCGHSA enrichment
  27. 2026-08-07 16:25 UTCEPSS rescore
  28. 2026-08-06 13:45 UTCEPSS rescore
  29. 2026-08-06 06:43 UTCEG score recompute
  30. 2026-08-06 06:43 UTCVendor advisory
  31. 2026-08-06 06:43 UTCGHSA enrichment
  32. 2026-08-05 19:15 UTCEPSS rescore
  33. 2026-08-05 19:15 UTCEPSS rescore
  34. 2026-08-05 10:11 UTCEG score recompute
  35. 2026-08-05 10:11 UTCVendor advisory
  36. 2026-08-05 10:11 UTCGHSA enrichment
  37. 2026-08-04 11:26 UTCEG score recompute
  38. 2026-08-04 11:26 UTCVendor advisory
  39. 2026-08-04 11:26 UTCGHSA enrichment
  40. 2026-08-04 10:36 UTCEPSS rescore
  41. 2026-08-04 10:21 UTCEG score recompute▲ 9.80
  42. 2026-08-04 10:21 UTCVendor advisory
  43. 2026-08-04 10:21 UTCGHSA enrichment
  44. 2026-08-04 10:19 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  45. 2026-08-03 10:34 UTCEPSS rescore
  46. 2026-08-02 02:25 UTCEPSS rescore
  47. 2026-08-02 02:25 UTCEPSS rescore
  48. 2026-08-01 04:14 UTCEPSS rescore
  49. 2026-07-30 16:26 UTCEPSS rescore
  50. 2026-07-30 01:29 UTCEPSS rescore
  51. 2026-07-28 15:34 UTCEPSS rescore
  52. 2026-07-28 15:34 UTCEPSS rescore
  53. 2026-07-27 03:09 UTCOSV refresh
  54. 2026-07-26 14:53 UTCEPSS rescore
  55. 2026-07-25 14:16 UTCEPSS rescore
  56. 2026-07-24 14:16 UTCEPSS rescore
  57. 2026-07-23 14:16 UTCEPSS rescore
  58. 2026-07-23 02:30 UTCEG score recompute
  59. 2026-07-22 23:16 UTCEG score recompute
  60. 2026-07-22 14:07 UTCEPSS rescore
  61. 2026-07-22 14:07 UTCEPSS rescore
  62. 2026-07-21 15:23 UTCEPSS rescore
  63. 2026-07-20 17:06 UTCEPSS rescore
  64. 2026-07-19 14:30 UTCEPSS rescore
  65. 2026-07-19 14:29 UTCEPSS rescore
  66. 2026-07-19 02:27 UTCEPSS rescore
  67. 2026-07-19 02:27 UTCEPSS rescore
  68. 2026-07-18 10:03 UTCEPSS rescore
  69. 2026-07-18 10:03 UTCEPSS rescore
  70. 2026-07-16 17:01 UTCEPSS rescore
  71. 2026-07-15 16:56 UTCEPSS rescore
  72. 2026-07-15 01:59 UTCEPSS rescore
  73. 2026-07-15 01:59 UTCEPSS rescore
  74. 2026-07-13 22:28 UTCEPSS rescore
  75. 2026-07-13 22:28 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-54269?
CVE-2023-54269 is a critical vulnerability published on December 30, 2025. 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 rqxprtctxt pointer is moved out of the svcrqst into the svcdeferred_req. When the deferred request is revisited, the pointer is copied into the…
When was CVE-2023-54269 disclosed?
CVE-2023-54269 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54269 actively exploited?
CVE-2023-54269 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.2% of all scored CVEs.
What is the CVSS score of CVE-2023-54269?
CVE-2023-54269 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54269?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54269, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54269

Explore →

Is Your Infrastructure Affected by CVE-2023-54269?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs