CVE-2026-31630

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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: proc: size address buffers for %pISpc output

The AF_RXRPC procfs helpers format local and remote socket addresses into fixed 50-byte stack buffers with "%pISpc".

That is too small for the longest current-tree IPv6-with-port form the formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a dotted-quad tail not only for v4mapped addresses, but also for ISATAP addresses via ipv6_addr_is_isatap().

As a result, a case such as

[ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535

is possible with the current formatter. That is 50 visible characters, so 51 bytes including the trailing NUL, which does not fit in the existing char[50] buffers used by net/rxrpc/proc.c.

Size the buffers from the formatter's maximum textual form and switch the call sites to scnprintf().

Changes since v1:

  • correct the changelog to cite the actual maximum current-tree case
explicitly
  • frame the proof around the ISATAP formatting path instead of the earlier
mapped-v4 example

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.1%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 1, 2026

Advisory Details (6)

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

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

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

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/625af53a1564e31bb2df9adc3739df46137f46c1
generic

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/386c86412608d3449006a318a662cbcd6ca1f668
generic

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/235b2115de892eab2e107a42efa7a4347baaa80b
generic

rxrpc: proc: size address buffers for %pISpc output - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10ebed83f9f6414af4e85bc85ffaeda7effdd874

Vendor Advisories for CVE-2026-31630(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 133 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31630?
CVE-2026-31630 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: proc: size address buffers for %pISpc output The AF_RXRPC procfs helpers format local and remote socket addresses into fixed 50-byte stack buffers with "%pISpc". That is too small for the longest current-tree IPv6-with-port…
When was CVE-2026-31630 disclosed?
CVE-2026-31630 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31630 actively exploited?
CVE-2026-31630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31630?
CVE-2026-31630 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31630, 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-31630

Explore →

Is Your Infrastructure Affected by CVE-2026-31630?

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

Start Free Scan →Browse All CVEs