CVE-2026-31639

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: Fix key reference count leak from call->key

When creating a client call in rxrpc_alloc_client_call(), the code obtains a reference to the key. This is never cleaned up and gets leaked when the call is destroyed.

Fix this by freeing call->key in rxrpc_destroy_call().

Before the patch, it shows the key reference counter elevated:

$ cat /proc/keys | grep afs@54321 1bffe9cd I--Q--i 8053480 4169w 3b010000 1000 1000 rxrpc afs@54321: ka $

After the patch, the invalidated key is removed when the code exits:

$ cat /proc/keys | grep afs@54321 $

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

rxrpc: Fix key reference count leak from call->key - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix key reference count leak from call->key - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix key reference count leak from call->key - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Fix key reference count leak from call->key - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/978108902ee4ef2b348ff7ec36ad014dc5bc6dc6
generic

rxrpc: Fix key reference count leak from call->key - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e6ef713b1598f6acd7f302fa6b12b6731c89914

Vendor Advisories for CVE-2026-31639(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.135—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (127 versions)6.19.13-1—

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 31× 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 220 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31639?
CVE-2026-31639 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix key reference count leak from call->key When creating a client call in rxrpcallocclient_call(), the code obtains a reference to the key. This is never cleaned up and gets leaked when the call is destroyed. Fix this by…
When was CVE-2026-31639 disclosed?
CVE-2026-31639 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31639 actively exploited?
CVE-2026-31639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31639?
CVE-2026-31639 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31639, 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-2026-31639

Explore →

Is Your Infrastructure Affected by CVE-2026-31639?

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

Start Free Scan →Browse All CVEs