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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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: 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)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 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

August 5, 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.

Patch Availability(1)

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

(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.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.13-1—

All Vendor Advisories

(11)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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 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-2026-31630 actively exploited?
CVE-2026-31630 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 96.9% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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