CVE-2026-31638

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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: Only put the call ref if one was acquired

rxrpc_input_packet_on_conn() can process a to-client packet after the current client call on the channel has already been torn down. In that case chan->call is NULL, rxrpc_try_get_call() returns NULL and there is no reference to drop.

The client-side implicit-end error path does not account for that and unconditionally calls rxrpc_put_call(). This turns a protocol error path into a kernel crash instead of rejecting the packet.

Only drop the call reference if one was actually acquired. Keep the existing protocol error handling unchanged.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
35.7%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (5)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

rxrpc: Only put the call ref if one was acquired - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Only put the call ref if one was acquired - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: Only put the call ref if one was acquired - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8299ca146489664e3c0c90a3b8900d8335b1ede4
generic

rxrpc: Only put the call ref if one was acquired - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6331f1b24a3e85465f6454e003a3e6c22005a5c5
generic

rxrpc: Only put the call ref if one was acquired - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c156aff8a2d4fa0d61db7837641975cf0e5452d

Vendor Advisories for CVE-2026-31638(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 41× 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 146 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31638?
CVE-2026-31638 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Only put the call ref if one was acquired rxrpcinputpacketonconn() can process a to-client packet after the current client call on the channel has already been torn down. In that case chan->call is NULL, rxrpctryget_call()…
When was CVE-2026-31638 disclosed?
CVE-2026-31638 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-31638 actively exploited?
CVE-2026-31638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31638?
CVE-2026-31638 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31638?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31638, 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

Explore the affected products and dependency analysis for CVE-2026-31638

Explore →

Is Your Infrastructure Affected by CVE-2026-31638?

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

Start Free Scan →Browse All CVEs