CVE-2026-31634

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 reference count leak in rxrpc_server_keyring()

This patch fixes a reference count leak in rxrpc_server_keyring() by checking if rx->securities is already set.

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
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

July 14, 2026

Advisory Details (10)

Auto-updated Jul 17, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ce36d28f67c2a477a7e2f03480de3f6783fb363
generic

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ee931c3cd97f1c42b4fbf057f04b9dae45dfb7a
generic

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45d9584e51bdd61faf1900f82666d4ea6a85da72
generic

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/139c750bf06649097d98b0bc41e2a678b4627e27
generic

rxrpc: fix reference count leak in rxrpc_server_keyring() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12de9e0e0b0b7058be7dfb8a5927eb565bc25780

Vendor Advisories for CVE-2026-31634(2)

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 @ 5.10.258osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
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 (124 versions)6.19.13-1

Additional Vendor Advisories

(24)

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 / 50× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31634?
CVE-2026-31634 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix reference count leak in rxrpcserverkeyring() This patch fixes a reference count leak in rxrpcserverkeyring() by checking if rx->securities is already set.
When was CVE-2026-31634 disclosed?
CVE-2026-31634 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31634 actively exploited?
CVE-2026-31634 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31634?
CVE-2026-31634 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31634?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31634, 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-31634

Explore →

Is Your Infrastructure Affected by CVE-2026-31634?

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